-
Notifications
You must be signed in to change notification settings - Fork 726
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
Multiple references field loses choices #591
Comments
Thanks for this detailed report. This is indeed a bug. I'm looking at it. For the port, how do you launch the demo? I access it at http://localhost:8000/ URL. |
The port problem was due to me playing around with the master branch of ng-admin-demo. It's README tells you to use the 3000 port while running on 3001. But actually it's default branch changed, so nevermind. |
This is most probably a bug with ui-select. I hope that Upgrading it will fix the bug. |
No it doesn't, and it's even worse (see angular-ui/ui-select#1398 by the way). Looking into an alternative solution. |
I read somewhere that the ui-select gents abandoned it since google's material design elements will probably be highly adopted by the angularjs community. https://material.angularjs.org/latest/demo/select I still don't see they have multi-select so I don't really get it but I'm sure it will come out soon enough. |
This happens if you edit some entity that has references saved in a reference-many-field. If you delete some choice from reference field, you can't select it back clicking, you have to go back and reenter the editing form.
For example in the demo application:
Go to the posts list and edit any post with tags.
Delete any tag. You can't select it back:
Sometimes i also experience this behavior, but it's not persistent. It happens when i go back to dashboard while editing via changing the url manually and pressing enter, and going back to edit form:
Anyway, if you type something, the list refreshes and everything start working fine, so i don't know if it's a bug or that's the expected behavior.
By the way, the README for ng-admin-demo tells you to go to localhost:3000 but the server.js runs on port 3001.
The text was updated successfully, but these errors were encountered: