api-guidelines
cool-webapi
api-guidelines | cool-webapi | |
---|---|---|
16 | 6 | |
22,411 | 50 | |
0.3% | - | |
8.8 | 1.3 | |
2 days ago | about 1 year ago | |
C# | ||
GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
api-guidelines
-
5 Things I wanted to know about REST API when I was starting
AZURE API Guidelines
-
Mastering API Design: 26 Resources for Software Engineers
📝 "Microsoft REST API Guidelines" [link]
- Ask HN: Any book recommendations for API design?
- What are the best practices that you, your team or your company follows while developing apis or while writing api contracts?
- Recommendations for resources about REST APIs?
- Best Practice/Standars for API Management endpoints
- Ask HN: Standards for API Error Responses
-
Recommendation reading (books/blogs) for best practices while designing REST APIs
This is a great, thorough and in-depth document from Microsoft: https://github.com/microsoft/api-guidelines/blob/vNext/Guidelines.md
-
Looking for understandable good practices concerning structure of json returned
Thing is, I made some researches this morning, and I found nowhere a "data" wrapper, not in Microsoft API best practices [FR] (client is using Microsoft APIs), not in Microsoft API guidelines, not in OpenAPI offical specifications, nowhere in any blog I found this morning.
-
Everything about APIs
Microsoft REST API guidelines
cool-webapi
-
What every ASP.NET Core Web API project needs - Part 6 - IServiceCollection Extension
So far I have added and configured several packages to the cool-webapi project and in the future articles I will add more packages and configuration and the Startup class will become a large class.
-
What every ASP.NET Core Web API project needs - Part 5 - Polly
You can find the source code for this walkthrough on Github.
-
What every ASP.NET Core Web API project needs - Part 4 - Error Message Reusability and Localization
Open Startup.cs class and follwing codes:
-
What every ASP.NET Core Web API project needs - Part 3 - Exception handling middleware
In the previous article, I wrote about API versioning and how to add Swagger to the sample project with support of API versioning. In this article, I show how to add custom middleware to handle exceptions globally and create a custom response when an error occurred.
-
What every ASP.NET Core Web API project needs - Part 2 - API versioning and Swagger
Open the cool-webpi project and Install Microsoft.AspNetCore.Mvc.Versioning.ApiExplorer package
-
What every ASP.NET Core Web API project needs - Part 1 - Serilog
Source code for this walkthrough could found on the Github.
What are some alternatives?
google.aip.dev - API Improvement Proposals. https://aip.dev/
serilog-ui - Simple Serilog log viewer UI for several sinks.
Sieve - ⚗️ Clean & extensible Sorting, Filtering, and Pagination for ASP.NET Core
Swashbuckle.AspNetCore - Swagger tools for documenting API's built on ASP.NET Core
free-for-dev - A list of SaaS, PaaS and IaaS offerings that have free tiers of interest to devops and infradev
Serilog - Simple .NET logging with fully-structured events
OpenAPI-Specification - The OpenAPI Specification Repository
serilog-sinks-mssqlserver - A Serilog sink that writes events to Microsoft SQL Server and Azure SQL
awesome-rest - A collaborative list of great resources about RESTful API architecture, development, test, and performance
ASP.NET Identity
aspnet-api-versioning - Provides a set of libraries which add service API versioning to ASP.NET Web API, OData with ASP.NET Web API, and ASP.NET Core.