Tagged articles
Image from Pexels

Tagged articles - Swagger

Found 16 articles tagged with Swagger

Supporting multiple authentication schemes in asp.net core webapi
Using more than one authentication schemes in webapi projects
0
Is is not so often than you have to use more than one authentication schemes in your project, but there are some corner cases when you have to do so. One of it is a scenario where you are supporting some weaker authentication schema like basic http authentication where credentials are supplied pretty much on every request. This kind of loosen security schema is to some limited extend suitable for internal APIs meaning that no other than users or most likely application within your organization network will access...read more
Handling file upload in ASP.NET Core 5 with Swagger UI
Generating proper file upload in Swagger UI for file upload in ASP.NET Core 5
0
In 2019 I worked on a REST API service which accepts files and stores them. Back then in .NET Core 2.2 I wrote custom Swagger operation filter which I described in article Handling file uploads in Swagger UI with ASP.NET Core...read more
Generic type controller methods in ASP.NET Core
Using generic type controller methods in ASP.NET Core with Swagger
0
Generic types are great way to re-use methods and apply the same logic to different types. However, they come with some limitations, especially in ASP.NET realm...read more
Representing available string values for parameters as list in Swagger ASP.NET Core
Valid values as list in Swagger UI in ASP.NET Core
 
0
Swagger is a great way do describe your RESTful API. In ASP.NET it is pretty easy to wire up your OpenAPI documentation with your service facade with Swashbuckle NuGet package...read more
Basic authentication with Swagger and ASP.NET Core
Setting up basic authentication in ASP.NET Core Web API projects
0
Basic authentication is not so popular authentication method nowadays. There is a valid reason for that and that is mainly the way credentials are used to authenticate to access the resources...read more
Dealing with default API versions in Swagger UI
Fixing additional routes in Swagger API when using default versions
0
Having your REST API versioned is important for evolving of the service over time. Especially if your service is exposed t multiple 3rd party clients...read more
Combining multiple Swagger API endpoints in a single UI
Multiple REST API microservices endpoints in a single Swagger UI
 
0
Shifting from traditional monolithic application architecture to micorservices can solve bunch of problems and issues monolith application application design approach introduces, but on the other hand it has it's own drawbacks, although number of drawbacks compared to number of problems it solves is a lot greater so it makes sense to take a path in process of moving from monolithic to micorservices. On of the steps to move to micorservices is to physically have your services running as individual processes...read more
Generation Java client libraries for REST service with swagger-gen Azure DevOps
Compiling and serving MAVEN packages for Java with Azure DevOps using PowerShell
0
Generating client libraries for REST API which are documented with Swagger can significantly reduce product development time, especially on the front-end side. Well documented API can be easily interpreted by various tools to generate language specific libraries which can be then just easily integrated in in the API service consuming application. Some time ago I wrote an article Stop writing clients in C# for your Web APIs which explains how to use NSwag to generate NuGet packages for Swagger documented Web API REST services and to push them to Azure DevOps Artifact Feed...read more
Ignoring properties from controller action model in Swagger using JsonIgnore
Excluding properties from Swagger in controller action input model using Newtonsoft.Json package
0
While designing the REST API, quite often you may find yourself in a situation where the data can be provided from multiple sources, like route, query string or POST/PUT payload. While that might not be a big problem, it may force you to redesign your models and most likely you will end up with keeping your original DTOs but then designing a new model in your application services layer just to have all your data from different sources in one place when you are passing it to the service method. Resolving multiple sources custom binding ...read more
Handling file uploads in Swagger UI with ASP.NET Core
Swagger UI file upload in ASP.NET Core WebApi
0
Swagger is the most convenient way to document your REST api endpoints. It provides generating of documentation on the fly based on the code structure, which shortens the time of creating the documentation drastically...read more
Stop writing clients in C# for your Web APIs
Auto generating client libraries and packages for Web API using NSwag and Azure DevOps
0
Times of writing your HttpClient setup to call REST API endpoint are over. It is just to much of repetitive code and taking care of the endpoints of the REST API service...read more
Localization of the DTOs in a separate assembly in ASP.NET Core
Localizing validation messages in ASP.NET Core WebAPI
0
Since REST services do not have the UI, there is not much space for the localization. Data is sent and retrieved and most of the decisions is made based on the status code of the response...read more
Displaying Azure DevOps build number in Swagger UI for ASP.NET Core
How to add and show Azure DevOps build number in ASP.NET Core project and Swagger UI
0
Swagger is a great way to document you REST API endpoints and reduce the need for communication, item spent and the cost for supporting the consumers of you APIs. Apart from providing the info about the endpoints, models, validation it can also display the data of the product...read more
DTO comments from external assembly in Swagger documentation in ASP.NET Core
Involving contract classes documentation from separate assemblies to Swagger
0
Contracts, models or DTOs, call them how ever you want, are your connection with the outside world from your REST API. Consumers of your API depend on them and they know what to expect or what your API endpoints expect in communication...read more
Setting up Swagger to support versioned API endpoints in ASP.NET Core
Adding Swagger support for versioned REST Web API endpoints
0
Versioning of your endpoints is important especially if you have 3rd party dependent clients of your REST API service. Any change in your endpoint, for example in data structure may impact clients even if it is backward compatible, clients may process your endpoint data in different ways, so even adding one additional property to your model may also impact functionality of the client which is consuming your endpoint. Prerequisites ...read more

.NET

read more

JavaScript

read more

SQL/T-SQL

read more

Umbraco CMS

read more