-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to parse text exception with in models with group-as/@in-json="SINGLETON_OR_ARRAY"
behavior
#221
Labels
bug
Something isn't working
Comments
This an invalid model because of the conflicting requirements between the parent max-occurs and the inner group-as. When
|
david-waltermire
added a commit
that referenced
this issue
Oct 28, 2024
aj-stein-gsa
added a commit
to aj-stein-gsa/metaschema
that referenced
this issue
Oct 29, 2024
This new constraint implements a check for the following issue comment. metaschema-framework/metaschema-java#221 (comment)
8 tasks
aj-stein-gsa
added a commit
to aj-stein-gsa/fedramp-automation
that referenced
this issue
Oct 29, 2024
This addresses changes that should be handled as determined by upstream guidance from metaschema-framework maintainers. metaschema-framework/metaschema-java#221 metaschema-framework/metaschema#44
aj-stein-gsa
added a commit
to aj-stein-gsa/fedramp-automation
that referenced
this issue
Oct 29, 2024
This addresses changes that should be handled as determined by upstream guidance from metaschema-framework maintainers. metaschema-framework/metaschema-java#221 metaschema-framework/metaschema#44
5 tasks
aj-stein-gsa
added a commit
to GSA/fedramp-automation
that referenced
this issue
Oct 29, 2024
* [skip ci] Metaschema module for unit test struct We are proposing changes to the structure of the JSON/YAML unit test file used for all constraints test suite management. This version documents the model of that YAML file before the proposed change in the comments of the #817 PR, linked below. #817 (comment) * [skip ci] Document unit test metaschema elements * [skip ci] Do not explicitly use default types * [skip ci] Add missing `@id` and `@level` to model * [skip ci] Add pipeline to pipeline, thx @wandmagic * [skip ci] Backport #219 docs into model remarks * [skip ci] Fix max-occurs re bad model cardinality This addresses changes that should be handled as determined by upstream guidance from metaschema-framework maintainers. metaschema-framework/metaschema-java#221 metaschema-framework/metaschema#44 * [skip ci] Is a pipeline with a ref even a pipeline at all? Thanks to @Rene2mt for PR feedback about the missing ref to the assembly definition of pipeline in the model. Co-authored-by: Rene Tshiteya <rene-claude.tshiteya@gsa.gov> --------- Co-authored-by: Rene Tshiteya <rene-claude.tshiteya@gsa.gov>
8 tasks
david-waltermire
added a commit
that referenced
this issue
Oct 30, 2024
Changed expected behavior in unit test to provide null values in JSON and empty values in XML, which is consistent with current behavior. Improved error handling for data type conformance issues. Related to GSA/fedramp-automation#823.
david-waltermire
added a commit
that referenced
this issue
Oct 30, 2024
Changed expected behavior in unit test to provide null values in JSON and empty values in XML, which is consistent with current behavior. Improved error handling for data type conformance issues. Related to GSA/fedramp-automation#823.
wandmagic
pushed a commit
to GSA/fedramp-automation
that referenced
this issue
Nov 1, 2024
* [skip ci] Metaschema module for unit test struct We are proposing changes to the structure of the JSON/YAML unit test file used for all constraints test suite management. This version documents the model of that YAML file before the proposed change in the comments of the #817 PR, linked below. #817 (comment) * [skip ci] Document unit test metaschema elements * [skip ci] Do not explicitly use default types * [skip ci] Add missing `@id` and `@level` to model * [skip ci] Add pipeline to pipeline, thx @wandmagic * [skip ci] Backport #219 docs into model remarks * [skip ci] Fix max-occurs re bad model cardinality This addresses changes that should be handled as determined by upstream guidance from metaschema-framework maintainers. metaschema-framework/metaschema-java#221 metaschema-framework/metaschema#44 * [skip ci] Is a pipeline with a ref even a pipeline at all? Thanks to @Rene2mt for PR feedback about the missing ref to the assembly definition of pipeline in the model. Co-authored-by: Rene Tshiteya <rene-claude.tshiteya@gsa.gov> --------- Co-authored-by: Rene Tshiteya <rene-claude.tshiteya@gsa.gov>
brian-ruf
pushed a commit
to brian-ruf/fedramp-automation
that referenced
this issue
Nov 8, 2024
* [skip ci] Metaschema module for unit test struct We are proposing changes to the structure of the JSON/YAML unit test file used for all constraints test suite management. This version documents the model of that YAML file before the proposed change in the comments of the GSA#817 PR, linked below. GSA#817 (comment) * [skip ci] Document unit test metaschema elements * [skip ci] Do not explicitly use default types * [skip ci] Add missing `@id` and `@level` to model * [skip ci] Add pipeline to pipeline, thx @wandmagic * [skip ci] Backport GSA#219 docs into model remarks * [skip ci] Fix max-occurs re bad model cardinality This addresses changes that should be handled as determined by upstream guidance from metaschema-framework maintainers. metaschema-framework/metaschema-java#221 metaschema-framework/metaschema#44 * [skip ci] Is a pipeline with a ref even a pipeline at all? Thanks to @Rene2mt for PR feedback about the missing ref to the assembly definition of pipeline in the model. Co-authored-by: Rene Tshiteya <rene-claude.tshiteya@gsa.gov> --------- Co-authored-by: Rene Tshiteya <rene-claude.tshiteya@gsa.gov>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using metaschema-java in the latest stable version to deserialize models with fields (not assemblies) with the
group-as/@in-json="SINGLETON_OR_ARRAY"
, you will consistently receive ajava.io.IOException: Unable to parse field value as text
exception.Who is the bug affecting
Developers of Metaschema processors operating on constraints and developers maintaining constraints
How do we replicate this issue
Expected behavior (i.e. solution)
The model is properly deserialized and content validation is processed to complete on this example document instance as valid.
Other comments
No response
The text was updated successfully, but these errors were encountered: