feat: support bigint type
#35
Merged
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
himself65
approved these changes
Sep 20, 2022
| @@ -46,7 +46,7 @@ export function createEasyType<Value> ( | |||
| store => store.colorspace[config.colorKey]) | |||
| return ( | |||
| <InputBase | |||
| value={value} | |||
| value={type === 'bigint' ? `${value}` : value} | |||
There was a problem hiding this comment.
just treat everything as ${value}
There was a problem hiding this comment.
I think we should detect the type in the createEasyType function. That's not what it supposed should do
There was a problem hiding this comment.
Yeah, type checking needs to be done in the function, not in the expression, but except for string and number, it seems that there are few types that need to be converted?
Closed
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.
Trying to add support for the
biginttype.