Closed DavidHuebner closed 3 years ago
Thanks for reporting! It should be fixed in master. I wait a bit in case you find more bugs, then I will release later this week. Is that an important bug/feature for you? I never understood nor used multipleReferencesAllowed.
Fantastic! Thanks again for your quick response. I encountered this problem when I deserialized/serialized a typesystem which was then incompatible with the original typesystem. I was not actually interested in the value of the multipleReferencesAllowed.
It is perfectly fine for now to work from the master branch / dev version. So, an immediate release is not needed.
Thanks again!
Hey @jcklie , would you mind triggering a release now? We want to release our code now and it would be great to work on a released dkpro-cassis version. Highly appreciated!
I released it, please have a try and close the bug when it works for you.
Describe the bug The String value
"false"
of the feature multipleReferencesAllowed is incorrectly parsed asTrue
.The problem is in the function
_get_elem_as_bool(elem)
intypesystem.py
wherebool(elem.text)
is called. For non-empty string values, this boolean is always True. We should use a slightly more advanced method to parse strings into booleans.To Reproduce Steps to reproduce the behavior:
Expected behavior String value
"false"
should correctly be parsed asFalse
(boolean).Error message
Please complete the following information: