-
Notifications
You must be signed in to change notification settings - Fork 22
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
The multipleReferencesAllowed flag on array features is not handled #187
Comments
reckart
added a commit
that referenced
this issue
Aug 18, 2021
…_all_fs #186 - Creating subtypes of inheritance-final types (arrays) is not prevented #187 - The multipleReferencesAllowed flag on array features is not handled - Consistently wrap arrays into their proper UIMA array types when deserializing - Tests and code updated because in order to access the array elements it is now necessary to access them via the `elements` property of the array wrapper - Add handling of the multipleReferencesAllowed flag in during (de)serialization
reckart
added a commit
that referenced
this issue
Aug 18, 2021
…ndled - Restore test data that was accidentally removed during the refactoring - Fixed tests subsequently
reckart
added a commit
that referenced
this issue
Aug 18, 2021
…ndled - Cleaning up - Added one more test
reckart
added a commit
that referenced
this issue
Aug 19, 2021
…ed-and-arrays' into feature/168-Experimental-JSON-CAS-support * feature/185-186-187-Handling-of-multipleReferencesAllowed-and-arrays: #187 - The multipleReferencesAllowed flag on array features is not handled #187 - The multipleReferencesAllowed flag on array features is not handled #187 - The multipleReferencesAllowed flag on array features is not handled #187 - The multipleReferencesAllowed flag on array features is not handled #187 - The multipleReferencesAllowed flag on array features is not handled #187 - The multipleReferencesAllowed flag on array features is not handled #186 - Creating subtypes of inheritance-final types (arrays) is not prevented #185 - Transitively referenced primitive arrays not returned by _find_all_fs #186 - Creating subtypes of inheritance-final types (arrays) is not prevented #187 - The multipleReferencesAllowed flag on array features is not handled
reckart
added a commit
that referenced
this issue
Aug 19, 2021
…ndled - Handle cases where the "elements" of an array is not an empty array but simply None
reckart
added a commit
that referenced
this issue
Aug 19, 2021
…ed-and-arrays' into feature/168-Experimental-JSON-CAS-support * feature/185-186-187-Handling-of-multipleReferencesAllowed-and-arrays: #187 - The multipleReferencesAllowed flag on array features is not handled
reckart
added a commit
that referenced
this issue
Aug 19, 2021
…g-to-resolve-feature-path * main: #187 - The multipleReferencesAllowed flag on array features is not handled #187 - The multipleReferencesAllowed flag on array features is not handled #187 - The multipleReferencesAllowed flag on array features is not handled #187 - The multipleReferencesAllowed flag on array features is not handled #187 - The multipleReferencesAllowed flag on array features is not handled #187 - The multipleReferencesAllowed flag on array features is not handled #187 - The multipleReferencesAllowed flag on array features is not handled #186 - Creating subtypes of inheritance-final types (arrays) is not prevented #185 - Transitively referenced primitive arrays not returned by _find_all_fs #186 - Creating subtypes of inheritance-final types (arrays) is not prevented #187 - The multipleReferencesAllowed flag on array features is not handled # Conflicts: # tests/test_typesystem.py
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The multipleReferencesAllowed on an array feature indicates if the array can be rendered as an XML attributed or not. If when rendered as an attribute, the array does not receive an ID. Also, if two FSes refer to the same array, this array will end up twice in the XMI.
To Reproduce
Expected behavior
If f.multipleReferencesAllowed is true, the array should be rendered as a separate element, otherwise as an attribute.
Please complete the following information:
The text was updated successfully, but these errors were encountered: