-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
REST routing precedence #5553
Comments
Alternatively, it would be very helpful to add some sort of debug logging indicating what method is being routed to for a given rest request url |
Please move your question to the Forum or Stack Exchange. @piotrekkaminski suggestion to improve debugging. |
@choukalos -- where would be the correct place to request improvements to the official documentation? |
@tanberry Please advise |
Thanks @mbrinton01 . Hi @nickmarx12345678 , please do share your thoughts and suggestions (and maybe even a PR with some contributions!) to our docs. For more info, see http://devdocs.magento.com/guides/v2.1/contributor-guide/contributing_docs.html. You can also click on the "Edit this page on GitHUb" link at the top of every page in devdocs.magento.com (excluding auto-generated Swagger docs). And, @keharper is our API writer, hit him up, please. ;-) |
@nickmarx12345678 please let us know if this issue can be closed or you need additional support. |
Close it On Wed, Sep 28, 2016, 5:01 AM Mark Brinton notifications@github.com wrote:
|
MQE-2046: remove deprecated entities usages in MFTF tests
Would like some clarification with regards to how URL matching on the rest API occurs on URL's that developers create in their routes.xml
For example if:
route1 =
GET /V1/myResource/:customerId
route2 =
GET /V1/myResource/:customerId/subResource
It's not clear if requesting the url
/V1/myResource/12345/subResource
will map to route1 with a customerId parameter of12345/subResource
or if it will map to route2 with a customerId parameter of12345
Similar permutations of this would be helpful to know as well such as:
route1 =
GET /V1/myResource/:customerId
route2 =
GET /V1/myResource/subResource
route3 =
GET /V1/myResource/subResource/:subResourceId
It's unclear which will be called with what argument if I request
/V1/myResource/subResource
The text was updated successfully, but these errors were encountered: