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
Since the search component works without having the valid options initially loaded (since there can be thousands of applicable options), there is no way to fully render a previously selected option. While we can display the selected value in the input, that value may not match what the app wants to display since the list options use label, while the rehydrated value uses value.
Currently, the problem lies elsewhere: the Search component always uses the displayString as the text to render in the input. When the component is loaded with a value, this value never reflects the selected value.
Since the search component works without having the valid options initially loaded (since there can be thousands of applicable options), there is no way to fully render a previously selected option. While we can display the selected value in the input, that value may not match what the app wants to display since the list options use
label
, while the rehydrated value usesvalue
.nrg-ui/packages/ember-core/src/components/form/search.gts
Lines 154 to 168 in 429c9f4
Currently, the problem lies elsewhere: the
Search
component always uses thedisplayString
as the text to render in the input. When the component is loaded with a value, this value never reflects the selected value.nrg-ui/packages/ember-core/src/components/form/search.gts
Line 368 in 429c9f4
The text was updated successfully, but these errors were encountered: