Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sets model to null on init #82

Open
rrzadzki opened this issue Jun 1, 2017 · 0 comments
Open

Sets model to null on init #82

rrzadzki opened this issue Jun 1, 2017 · 0 comments

Comments

@rrzadzki
Copy link

rrzadzki commented Jun 1, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant