-
-
Notifications
You must be signed in to change notification settings - Fork 868
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
Route name generation is not working as before #5008
Comments
With the metadata backward compatibility flag to |
In 2.7 with the flag set to true but without migrating operations to the new way : it works Why this behavior has change ? Is it something that will come back ? |
Same here. api route names are different with new metadata system BUT ALSO metadata backward compatibility is |
I've seen a strange behavior (I don't know if it's normal or not) When I define operation like this (and define a name for the route) :
The debug:router works as expected. But if I do it this way :
The route name defined here is not taken into account. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
API Platform version(s) affected: 2.7.0
Description
In previous version when I did a
bin/console debug:router
all the route generated by API Plateform had a generated name which I was able to use as reference in my project.When upgrading to 2.7 it's not the case anymore.
Before :
After :
How to reproduce
Have some entities in 2.6.8 then upgrade to 2.7.0
Run each time :
bin/console debug:router
Possibile workaround
Add
name
property in each operations and name it as API plateform did before.The text was updated successfully, but these errors were encountered: