Skip to content

Fix wrong issue for valid min/max in class property#356

Merged
lilleyse merged 1 commit intomainfrom
fix-class-property-min-max-validation
Jan 6, 2026
Merged

Fix wrong issue for valid min/max in class property#356
lilleyse merged 1 commit intomainfrom
fix-class-property-min-max-validation

Conversation

@javagl
Copy link
Copy Markdown
Contributor

@javagl javagl commented Jan 6, 2026

Fixes #355 :

A validation issue was erroneously added to the report when a non-scalar class property defined (valid) min/max properties.

The reason was simply a missing return. It continued the validation there, assuming that the property was an array, even though it wasn't.

There currently are validation/spec files like the FullMetadataSchema.json and the validSchema.json for the baseline checks of valid schemas. But these do not explore the full range of possible valid schemas. I.e. they don't contain all (valid) combinations of things like min/max/offset/scale/required/noData/... etc. A new file, validSchemaWithMinMax.json, is added here, as a regression test. Approaches for more systematically generating 'all' valid schemas might be considered.

@lilleyse lilleyse merged commit c97548f into main Jan 6, 2026
2 checks passed
@lilleyse lilleyse deleted the fix-class-property-min-max-validation branch January 6, 2026 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Wrong type check for min/max in class properties

2 participants