You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello.
Not sure if bug or feature request:
In projects dealing with APIs, it can happen that you know the value of a select (eg a ressource id provided as query param) before you have fetched the list of options.
Currently if you do that, the select stays in its default state, showing no option selected.
Hello.
Not sure if bug or feature request:
In projects dealing with APIs, it can happen that you know the value of a select (eg a ressource id provided as query param) before you have fetched the list of options.
Currently if you do that, the select stays in its default state, showing no option selected.
Sample code
Expected behavior
When setting a value first, then the options, the component should render as selected if an option is matching the value
The text was updated successfully, but these errors were encountered: