feat(ui): introduce FieldType.Boolean - WF-165
#732
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
madeindjs
changed the title
FieldType.Boolean - WFFieldType.Boolean - WF-165
madeindjs
force-pushed
the
WF-165
branch
3 times, most recently
from
444370a to
7449183
Compare
This new field is just an alias for `FieldType.Text` but it will
make `useEvaluator` parse the value and accept `"yes"` or `True`
and return the boolean value.
This unlock the usage of boolean value in the state like:
```py
wf.init_state({
"string": "yes",
"true": True,
})
```
This is also the first step to introduce a new field setting UX for
boolean value (like a checkbox or something).
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.
This new field is just an alias for
FieldType.Textbut it will makeuseEvaluatorparse the value and accept"yes"orTrueand return the boolean value.This unlock the usage of boolean value in the state like:
This is also the first step to introduce a new field setting UX for boolean value (like a checkbox or something).