* Improves rule number handling
Adds a fallback mechanism for retrieving rule numbers.
This ensures the system can handle cases where the primary
"Rule Number" field is missing or empty, defaulting to "Rule #"
to maintain data integrity.
Also corrects some docstring formatting.
* Improves rule processing efficiency
Avoids unnecessary rule processing by checking rule severity against the minimum configured severity level. Also ensures that results are only attached to failed objects if they exist and meet the minimum severity criteria. Addresses a potential issue where rules with no "Report Severity" column could cause errors, by considering an alternative "Severity" column.
* Adds Python compatibility inspection
Ensures that the project is compatible with Python 3 by adding a compatibility inspection setting.
This will help to identify and address any potential compatibility issues early on.
* Updates integration test URL and severity.
Updates the default URL used in the integration test to a new speckle model checker endpoint.
Changes the minimum severity level from warning to info, increasing the detail of reported results.
* Updates Model Checker documentation
Updates the documentation to reflect the shift from a spreadsheet-based rule definition to the new Model Checker Application.
Explains how to access the application, create rules, and configure automations.
Also introduces the alternative TSV file format for programmatically generating rules or version controlling rules.
Jonathon Broughton