-
-
Notifications
You must be signed in to change notification settings - Fork 911
Proposal: Ability to specify identifier property of custom item operations #2126
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
Conversation
Hello
But i still have the same error with "Invalid identifier value or configuration" . Any issue please ? |
This should probably not be in the route defaults. |
@AbbesBendaoud10 It's not implemented yet. |
👍 should be a new attribute |
Any news regarding this? |
e006023
to
2010727
Compare
2010727
to
d4aec53
Compare
@soyuka @AbbesBendaoud10 how did you resolved that, I spent 2 days but nothing, would you help please, thank you. |
@lamb0tiana i did it with "_api_receive"=false. |
Use a custom route with a custom controller / data provider. |
@AbbesBendaoud10 Thanks it worked for me 🥇 |
When declaring a custom item operation, you often want to use another property as identifier, for example:
Today, this only works if you add a custom controller, either by using your own data or by calling the core data provider with new identifiers
['isbn' => 1]
.My proposal is to add a property in the operation route defaults:
By using this you have nothing else to add (no controller, no data provider), it'll just use the
isbn
property as identifier.This is a WIP, to be done: