cleanup

Author: nllong

.gitignore

@@ -16,4 +16,3 @@ geojson.xsd
 *.bak
 *.ipynb
 node_modules
-

.pre-commit-config.yaml

@@ -29,6 +29,6 @@ repos:
     hooks:
       # Run the linter
       - id: ruff
-        args: [--fix, --exit-non-zero-on-fix, --output-format=full]
+        args: [--fix, --exit-non-zero-on-fix, --output-format=full] #, --unsafe-fixes]
       # Run the formatter
       - id: ruff-format

docs/developer_resources.md

@@ -5,10 +5,13 @@
 Details of the deprecation policy are included in the BuildingSync XML schema file.
 
 ## Pull Requests
+
 ### Summary
+
 BuildingSync uses Pull Requests (PRs) to track and report changes to users when creating releases. Specifically, we document changes to the schema/repo by using labels on PRs, thus we require developers to add labels to all PRs. Our CI will validate labels.
 
 ### Requirements
+
 - PRs are our "source of truth" for important changes to the repo/schema
 - We encourage separate PRs for each "logical"/"discrete" change to the schema (especially if the changes are impactful/non-trivial to users). For example, removing an element from the schema should be separate from adding a choice to an unrelated element.
 - The labels for the PR indicate the implications of the changes. Our CI system will validate your labels. See [CI Labels](../.github/workflows/CI_Labels.yml) for more info.

docs/gbXML_reference.md

@@ -4,12 +4,12 @@ BuildingSync can reference the gbXML schema to allow gbXML-valid geometry data t
 
 There are two examples in the examples folder:
 
-* `Single_building_gmxml_externalreference_geometry.xml`
-* `Multi_building_gmxml_externalreference_geometry.xml`
+- `Single_building_gmxml_externalreference_geometry.xml`
+- `Multi_building_gmxml_externalreference_geometry.xml`
 
 The examples are basic mockups of BuildingSync files with gbXML geometry data, showcasing the formatting of an end-case XML file and which validate against the both BuildingSync and gbXML schema while containing foreign gbXML data. The gbXML elements allowed are prefixed with (namespaced) with `gbXML`.
 
-The elements are primarily geometry-specific elements that are children of gbXML's `<Space>` element and can be placed inside of a BuildingSync `<Space>` element.  Note that any existing IDref-type attributes in the gbXML data may cause validation errors (depending the XML validator strictness), as they are referencing ID's of elements that are from the original gbXML instance file, which will not be present in the BuildingSync instance file.  These can be removed a variety of ways; here's a simple XSLT transformation which can be applied to the document:
+The elements are primarily geometry-specific elements that are children of gbXML's `<Space>` element and can be placed inside of a BuildingSync `<Space>` element. Note that any existing IDref-type attributes in the gbXML data may cause validation errors (depending the XML validator strictness), as they are referencing ID's of elements that are from the original gbXML instance file, which will not be present in the BuildingSync instance file. These can be removed a variety of ways; here's a simple XSLT transformation which can be applied to the document:
 
 <pre><code>
 &lt;xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"&gt;
@@ -22,4 +22,3 @@ The elements are primarily geometry-specific elements that are children of gbXML
 &lt;/xsl:stylesheet&gt;
 </code>
 </pre>
-

docs/linking_elements.md

@@ -2,7 +2,7 @@ Here you can find Jupyter Notebooks which serve as guides for using BuildingSync
 
 # Setup
 
-From the root directory of the repo, run the following commands to set up the environment. 
+From the root directory of the repo, run the following commands to set up the environment.
 
 - `pip install poetry`
 - `poetry install`