We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Given the following code fragment:
@Relation("HAS_ITEM") List<YMLSequenceDescriptor> getSequences(); @Relation("HAS_ITEM") List<YMLMapDescriptor> getMaps(); @Relation("HAS_ITEM") List<YMLScalarDescriptor> getScalars();
And assuming that any of the three collections contains three elements, then calling .size() on every collection returns 3.
.size()
IMHO the correct behaviour would be, that only the collection for sequences should return 3, while all other shoudl return only zero.
The text was updated successfully, but these errors were encountered:
Duplicates #172
I'd like to treat this more as a feature than a bug: The model in the datastore is ambiguous, XO shall be able to compensate for that.
Sorry, something went wrong.
No branches or pull requests
Given the following code fragment:
And assuming that any of the three collections contains three elements, then calling
.size()
on every collection returns 3.IMHO the correct behaviour would be, that only the collection for sequences should return 3, while all other shoudl return only zero.
The text was updated successfully, but these errors were encountered: