Update Web API scaffolders to use new Web API conventions
See original GitHub issueWe are adding some new Web API specific conventions that we will need the Web API scaffolders to react to.
We are adding [ApiController]
attribute as the way to opt-in to new API specific conventions and behaviors that are tuned around best practices for APIs.
This will include:
- Automatically responding with a 400 when validation errors occur (using https://tools.ietf.org/html/rfc7807)
- Infer smarter defaults for action parameters (
[FromBody]
for complex types,[FromRoute]
when possible, otherwise[FromQuery]
)
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (10 by maintainers)
Top Results From Across the Web
Use web API conventions
Web API conventions are a substitute for decorating individual actions with [ProducesResponseType] . A convention allows you to:
Read more >Scaffolding for ASP.NET Core projects comes to Rider ...
Scaffolding makes development using ASP.NET MVC, ASP.NET Web API, or Razor Pages faster and more smooth. Let's take a look at how the...
Read more >Asp.Net Core Web API CRUD Operations Using EF ... - YouTube
Net Core Web API Project 01:24 - CRUD Operations in a Restfull API ... with Given ID 41:38 - Update Operation using PUT...
Read more >Scaffolding .NET Web APIs Powered By EF Core ... - YouTube
Do you need to build Web APIs with .NET & ASP.NET Core? Stop writing all of the code manually and let Visual Studio...
Read more >Enterprise-quality API Step 1: Scaffold your project
NET WebAPI with .NET 5. You can simply go through File > New Project or dotnet new and scaffold the required structure of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@vijayrkn @muratg - yes, the corresponding PR #772 was merged on Tuesday I believe.
So I’ll close this issue.
@seancpeters Is this already merged?