noOptionsMessage #3676
Merged
noOptionsMessage #3676
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
It should be `noOptionsMessage`, not `noOptionsMessageCSS`, because otherwise it throws Flow error: ```Cannot create `Select` element because property `noOptionsMessage` is missing in `StylesConfig` [1] but exists in object literal [2] in property `styles`.```
|
@wiesys maybe you can change |
Changed `loadingMessageCSS?: StyleFn`, to `loadingMessage?: StyleFn`.
|
Sure, no problem, @VasiliKubarka. |
🦋 Changeset is good to goLatest commit: ae1c673 We got this. Not sure what this means? Click here to learn what changesets are. |
This was referenced Oct 2, 2019
Merged
This was referenced Sep 12, 2021
This was referenced May 13, 2022
This was referenced May 13, 2024
This was referenced May 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
It should be
noOptionsMessage, notnoOptionsMessageCSS, because otherwise it throws Flow error:Cannot create `Select` element because property `noOptionsMessage` is missing in `StylesConfig` [1] but exists in object literal [2] in property `styles`.