More documents
@xuzhg is already working on this.
Since Nov 2, 2020.
- Dominant language
- C#
- Stars
- 505
- Forks
- 186
- PR merge metrics
- No merged PRs in 30d
Description
We recently upgraded to Net 5 preview and found out about yet another OData nuget package for .Net Core (we used to get https://github.com/OData/WebApi/tree/master/src/Microsoft.AspNetCore.OData).
There are many breaking changes. Routing above all confuses me. To make matters worse Swagger also stopped working giving this exception
Actions require an explicit HttpMethod binding for Swagger/OpenAPI 3.0
while there is already method declaration attributes above all actions. I even don't know if ODataRoute attributes still make sense or we should just simply use Routes.
Everything is messy and the whole transition looks crud, nondeterministic, haphazard and unclear. All previous tips and tricks on the web that used to work are a rolling dice now. You have to simply go with trial and error to look which is which and what features are still there and you can count on.
Please, do provide more documents and samples, with the lastest changes in mind. Now! Not a year from now! Do not refer to some repository from 10 years ago of WebApi ages. Not everyone can afford the time for this many breaking changes and find their way through source codes, so please be more caring and speak to the community! Just two simple (and repetitive in content) articles on devblogs with absolutely bare minimum use case scenario cannot cover all the promised and relied features of previous versions...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.