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 have a controller for managing an instance of an angular resource, here a Contract, and a selector for choosing a Venue for the property Contract.Venue.
Selecting the venue with the selector works correctly; the property is set and saved to the server. On refresh however, the selector does not display the current value and in fact sets Contract.Venue to null on init.
Expected behavior: as with a <select...> using ng-options, I expect the selector to be able to use an index field to recall the correct value from the list. Since the list of Venues is pulled through another async call which may be causing the problem, at the very least I would expect the selector NOT to modify the model before its remote options load.
The text was updated successfully, but these errors were encountered:
I have a controller for managing an instance of an angular resource, here a Contract, and a selector for choosing a Venue for the property Contract.Venue.
Selecting the venue with the selector works correctly; the property is set and saved to the server. On refresh however, the selector does not display the current value and in fact sets Contract.Venue to null on init.
Expected behavior: as with a <select...> using ng-options, I expect the selector to be able to use an index field to recall the correct value from the list. Since the list of Venues is pulled through another async call which may be causing the problem, at the very least I would expect the selector NOT to modify the model before its remote options load.
The text was updated successfully, but these errors were encountered: