[RFR] Migrate NullableBooleanInput to TypeScript #3523
Merged
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
djhi
force-pushed
the
nullable-boolean-input-typescript
branch
from
a76c4f9 to
2cff61e
Compare
Kmaschta
reviewed
Aug 15, 2019
| @@ -38,7 +40,7 @@ const NullableBooleanInput = ({ | |||
| validate, | |||
| ...rest | |||
| }) => { | |||
| const classes = useStyles(); | |||
| const classes = useStyles({}); | |||
There was a problem hiding this comment.
Just curiosity, but why is the impact of the brackets as arguments of useStyles?
There was a problem hiding this comment.
None. See mui/material-ui#16867
There was a problem hiding this comment.
In a nutshell, it's a workaround for TypeScript
fzaninotto
approved these changes
Aug 19, 2019
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.
Follow #3522