Allow default exposed value to be false or any empty data
#371
Conversation
This file contains hidden or 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
Using `present?` limits what can be set as `:default` and restricts falsy values like `false`, `''`, `[]` for example. I don't really see why not allow those (I have a use case for `false` for example, which is to ensure a nullable boolean value is always rendered as a boolean).
pawelma
approved these changes
Dec 15, 2022
|
ok makes sense … thanks @norydev |
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.
Using
present?limits what can be set as:defaultand restricts falsy values likefalse,'',[]for example.I don't really see why not allow those (I have a use case for
falsefor example, which is to ensure a nullable boolean value is always rendered as a boolean).