-
Notifications
You must be signed in to change notification settings - Fork 730
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
Edit identity (primary key) field #332
Comments
Good point, that will need to be addressed some time in the future. Until we face the problem ourselves, would you like to work on a patch? |
Well, that wasn't a part of my plans... But I'll try to spare some of my time on it. |
vasiakorobkin
pushed a commit
to vasiakorobkin/ng-admin
that referenced
this issue
Feb 27, 2015
fzaninotto
added a commit
that referenced
this issue
Mar 18, 2015
fix: Edit identity (primary key) field (#332 issue on GitHub)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given:
Problem:
When I try to edit name custom primary key setting it to, for example, "def", ng-admin sends modified entity element via PUT request to _/product/def_ URL. But no corresponding entity element does exist on this URL at the moment, so back-end fails to save changes.
Suggested solution:
To make ng-admin send PUT request to _/product/abc_ URL, using the original name value "abc" even if it was modified to "def". I think this should be default behavior.
The text was updated successfully, but these errors were encountered: