Skip to content
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

OData controller error - No HTTP resource was found that matches the request URI #56

Closed
coni2k opened this issue Mar 26, 2016 · 1 comment
Labels

Comments

@coni2k
Copy link
Contributor

coni2k commented Mar 26, 2016

Find 'em & destroy 'em

@coni2k coni2k added the bug label Mar 26, 2016
@coni2k
Copy link
Contributor Author

coni2k commented Mar 26, 2016

In the previous version, while doing naming convention check & fix, "key" variables were renamed to "id" in OData controllers.

However, "key" was actually a fixed and mandatory variable in ODataControllers. All "id" variables were renamed back to "key" again.


Method Signatures

Here are some rules for the method signatures:

  • If the path contains a key, the action should have a parameter named key.
  • If the path contains a key into a navigation property, the action should have a parameter named relatedKey.
  • Decorate key and relatedKey parameters with the [FromODataUri] parameter.
  • POST and PUT requests take a parameter of the entity type.
  • PATCH requests take a parameter of type Delta, where T is the entity type.

[http://www.asp.net/web-api/overview/odata-support-in-aspnet-web-api/odata-routing-conventions](Routing Conventions in ASP.NET Web API 2 Odata)

@coni2k coni2k closed this as completed in b825370 Mar 31, 2016
coni2k added a commit that referenced this issue May 19, 2016
This closes #53, closes #54, closes #55 and closes #56
coni2k added a commit that referenced this issue May 21, 2016
This closes #53, closes #54, closes #55, closes #56 and closes #57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant