OpenApiLINQPadDriver 0.0.4-alpha

OpenApiLINQPadDriver for LINQPad 7

Description

OpenApiLINQPadDriver is LINQPad 7 dynamic data context driver for creating C# clients based on Open API/Swagger specifications

• Specification is read using NJsonSchema and clients are generated using NSwag

Websites

• This project
• Original project for LINQPad 5
• UI is heavily inspired by CsvLINQPadDriver

Downloads

generation of lpx6 files is on the roadmap, for now we only support instalation via nuget

Prerequisites

• LINQPad 7: .NET 7/.NET 6

Installation

LINQPad 7

NuGet

• Open LINQPad 7.
• Click Add connection link.
• Click button View more drivers...
• Click radio button Show all drivers and type OpenApiLINQPadDriver (for now it is also required to check Include Prerelease checkbox)
• Install.
• In case of working in environments without internet access it is possible to manually download nuget package and configure Package Source to point to a folder where it is located

Usage

Open API Connection can be added the same way as any other connection.

• Click Add Connection
• Select OpenApi Driver
• Enter Open Api Json Uri or click Get from disk and pick it from file
• Manually enter API Uri or click Get from swagger.json, if servers are found in the specification uri of the first one will be picked
• Set settings
• Click OK
• Client should start generation, you can use it by right clicking on it and choosing Use in Current Query or by picking it from Connection select
• It is possible to drag method name from the tree view on the left to the query
• Example code using PetStore API

async Task Main() 
{
  var newPetId = System.Random.Shared.NextInt64();
  await PetClient.AddPetAsync(new Pet() 
  {
    Id = newPetId,
    Name = "Dino",
    Category = new Category 
    {
        Id = 123,
        Name = "Dog"
    }
  });

  await PetClient.GetPetByIdAsync(newPetId).Dump();
}

Refreshing client

• Right click on the connection and click Refresh
• Or use shortcut Shift+Alt+D

Configuration Options

Client Generation

• Endpoint grouping - how methods will be grouped in generated client
  • Multiple clients from first tag and operationName - usually first tag corresponds to ASP.NET controller, so this will group methods by controller
  • Single client from OperationId and OperationName - this will put all endpoints in one class
• Json library - library used in generated client for serialization/deserialization, for specification reading NJsonSchema uses Newstonsoft.Json
  • System.Text.Json
  • Newstonsoft.Json
• Class style
  • POCOs (Plain Old C# Objects)
  • Classes implementing the INotifyPropertyChanged interface
  • Classes implementing the Prism base class - WIP, the library that is required is not added to the compilation
  • Records - read only POCOs (Plain Old C# Objects)
• Generate sync methods - by default sync methods will not be generated
• Build in Release - Build generated code in Release, default: false

Misc

• Debug info: show additional driver debug info, e.g. generated data context sources, add Execution Times explorer item with execution times of parts of the generation pipeline and will add warnings from the compilation if any were present
• Remember this connection: connection will be available on next run.
• Contains production data: files contain production data.

PrepareRequestFunction

• Each generated client has PrepareRequestFunction Func, for Multiple clients from first tag and operationName mode, helper set only Func is also generted to set them all at once
• This Func will be run on each method exectuion before making a http request, it is run in PrepareRequest partial methods generated by NSwag
• It can be used to set additional headers or other http client settings
• Example usage

async Task Main() 
{
  PrepareRequestFunction = (httpClient, requestMessage, url) => 
  {
    requestMessage.Headers.Add("UserId", "9");
    requestMessage.Headers.Authorization = new System.Net.Http.Headers.AuthenticationHeaderValue("Bearer", "<token>");
  };
}

async Task Main() 
{
  PrepareRequestFunction = PrepareRequest;
}

private void PrepareRequest(HttpClient httpClient, HttpRequestMessage requestMessage, string url) 
{
  requestMessage.Headers.Add("UserId", "9");
  requestMessage.Headers.Authorization = new System.Net.Http.Headers.AuthenticationHeaderValue("Bearer", "<token>");
}

Known Issues

• Code does not compile when there are parameters with the same name, but with case differences in the single endpoint and they come from different locations eg [FromQuery] int test, [FromHeader] int Test related issue

Credits

Tools

• LINQPad 7
• LINQPad Command-Line and Scripting (LPRun)

Libraries

• NJsonSchema
• NSwag
• Newtonsoft.Json - required by NSwag, included to bump version

Development

• OpenApiLINQPadDriver.csproj contains special Debug_Publish_To_LINQPad_Folder debug build configuration, if it is chosen, code will be build only targeting net7.0-windows with additional properties
• LINQPad can pick drivers from \LINQPad\Drivers\DataContext\NetCore folder
• Additionaly when exceptions will be thrown it will be possible to attach a debugger

Roadmap

• Allow injection of own httpClient
• Unit tests
• PrepareRequest with string builder overload
• ProcessResponse
• PrepareRequest and ProcessResponse async overload that could be set via a setting
• Methods parameters and responses in tree view
• Auto dump response
• Auth helper methods eg. SetBearerToken
• Check if it is possible to add summary to generated methods
• Add Prism.Mvvm to compilation when prism class style is picked
• When multiple servers are found allow selection
• LINQPad 5 support
• Examples (include in the nuget) - possibly the same ones could be used in testing
• Expose JsonSerializerSettings setter on multi client setup
• Expose ReadResponseAsString on multi client setup
• Treat warnings as errors in generated code (generalDiagnosticOption: ReportDiagnostic.Error)