loadOptions not properly typed anymore
See original GitHub issue- The argument
inputValue
provided toloadOptions
is inferred with typeany
, instead ofstring
(unless the second argument, callback, is also extracted) -> type overload seems to be broken. - The return value of
loadOptions
can be anything, no type error is ever reported.
See example: https://codesandbox.io/s/react-select-v5-ts-9sxmq
This worked prior to v5
Issue Analytics
- State:
- Created 2 years ago
- Comments:8
Top Results From Across the Web
React-Select Async loadOptions is not loading options properly
React Async Select loadoption sometimes fail to loads the option. This is a very strange phenomenon after couple of set of queries react ......
Read more >React-Select Async loadOptions is not loading options properly
I mean there blank options loaded, no text value. yes you are right, is a synchronous method returning a string, i don't need...
Read more >LOAD command - Db2 - IBM
The LOAD command loads data at the page level, bypasses trigger firing and logging, and delays constraint checking and index building until after...
Read more >Create, load, or edit a query in Excel (Power Query)
Set query load options. You can load a Power Query: To a worksheet. In the Power Query Editor, select Home > Close &...
Read more >Assembly-CSharp-Editor.csproj could not be loaded
The sln is not updated correctly and the -Editor.dll fails to create. One reason you possibly do not have a script there anymore...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I made a PR to go back to the old type.
Scratch that, let me rethink the solution.