Fix "true" value handling in boolean components (checkbox/switch) #195
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When creating a new entity with a form, a boolean value will be send as object
true(which is valid ttl syntax).Interestingly, when updating an entity (which would happen via a PUT request), the ttl will instead use
"true"^^xsd:boolean. (as far as I could find, also valid).When requesting the boolean value, the same syntax (
"true"^^xsd:boolean) is used, but the boolean-aware components expect ("1"^^xsd:boolean). This makes it so they can handle both "true" and "1".Fixing it here seemed the most logical.
some helper function might make sense, so it can also be used by developers creating custom components?