RobSlgm
commented
10 months ago Using the AddOpenApiDocument call to set a flat hierarchy solves the first issue and allows compilation again.
namespace Net80NJsonSchema11;
using System.Text.Json;
using NJsonSchema;
using NJsonSchema.Generation;
public class Program
{
public static void Main(string[] args)
{
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddEndpointsApiExplorer();
builder.Services.AddOpenApiDocument(c =>
{
c.SchemaSettings = new SystemTextJsonSchemaGeneratorSettings
{
SchemaType = SchemaType.OpenApi3,
FlattenInheritanceHierarchy = true,
};
});
builder.Services.AddControllers().AddJsonOptions(o => o.JsonSerializerOptions.Converters.Add(new NetTopologySuite.IO.Converters.GeoJsonConverterFactory()));
// builder.Services.AddSwaggerDocument();
var app = builder.Build();
app.MapControllers();
app.Run();
}
}If you exclude further types, e.g "excludedTypeNames" in nswag.json: "LazyOfPrecisionModel", "SortIndexValue" the generated api.ts is basically the same as with sdk 7.
But in both version (7 / 8) the OpenApi definition while using NetTopologySuite NetTopologySuite is misleading or wrong, hence the reason why you exclude types or I use for very restricted use cases ITypeMapper.
rootix
I'm in the process of upgrading a .NET 7 based solution which uses Nswag assembly scanning to .NET 8 with the .csproj approach.
I get an error with our use of NetTopologySuite geometries on the upgraded solution:
For testing purposes, i switched the .NET 7 version over to the .csproj approach where it worked.
I prepared a minimal sample repository with 2 projects (MsBuild AfterBuildTarget):
https://github.com/rootix/NJsonSchemaIssue
Everything except the updated .NET version and the updated Packages (Nswag 14 Preview 12) is the same.
Am i missing something? I tried to add "Coordinate" to the ExcludedTypeNames, but with no luck. And it worked in the older version anyway.
Thanks for the help!