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
I've searched for existing issues that already report this problem, without success. | J’ai vérifié parmi les tickets (issues) existants que ce sujet n’avait pas déjà été soumis.
Describe the feature request. | Décrivez la fonctionnalité demandée
Currently, select options are difficult to work with when they are populated by values received from API calls.
For example:
Since "options" are empty when page is loaded, the select component will be empty.
The "for" loop is removed once the component is generated once, so it doesn't get updated when the options are received from the server.
It makes it difficult to refresh the value dynamically.
Describe the use case. | Décrivez les cas d’utilisation
Useful when the options are being loaded or changed.
Describe the preferred solution. | Décrivez la solution souhaitée
No response
Describe all alternatives. | Décrivez toutes les solutions possibles
No response
Provide related code or examples. | Fournissez du code ou des exemples pertinents
No response
Add other relevant resources. | Ajoutez toute autre ressource utile
No response
The text was updated successfully, but these errors were encountered:
Hey @AlexisLeblancDFO In our v0.26.3 update we did some work to address this within the gcds-select. Would you be able to test and see if you are still having this issue on that version of gcds-components?
Vue uses the key property internally to manage what it re-renders. By changing the key property, it forces a re-render of the select with the new options. Can be seen in the same stackblitz linked above.
Prerequisites | Prérequis
Describe the feature request. | Décrivez la fonctionnalité demandée
Currently, select options are difficult to work with when they are populated by values received from API calls.
For example:
Since "options" are empty when page is loaded, the select component will be empty.
The "for" loop is removed once the component is generated once, so it doesn't get updated when the options are received from the server.
It makes it difficult to refresh the value dynamically.
Describe the use case. | Décrivez les cas d’utilisation
Useful when the options are being loaded or changed.
Describe the preferred solution. | Décrivez la solution souhaitée
No response
Describe all alternatives. | Décrivez toutes les solutions possibles
No response
Provide related code or examples. | Fournissez du code ou des exemples pertinents
No response
Add other relevant resources. | Ajoutez toute autre ressource utile
No response
The text was updated successfully, but these errors were encountered: