You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When generating an OpenAPI specifications, the paths and components are not sorted in the same order when compiling on Windows vs. Docker. Perhaps the sort order is not specified by NSwag and therefore somewhat arbitrary? That would explain why different instances of .NET cause different outputs.
Feature suggestion: Automatically sort paths and components.
Background for why this is important: I want generation of the OpenAPI spec to be deterministic, so that I more easily can check for unexpected changes.
As a workaround, I have added a document processor:
Thanks for a great library!
When generating an OpenAPI specifications, the paths and components are not sorted in the same order when compiling on Windows vs. Docker. Perhaps the sort order is not specified by NSwag and therefore somewhat arbitrary? That would explain why different instances of .NET cause different outputs.
Feature suggestion: Automatically sort paths and components.
Background for why this is important: I want generation of the OpenAPI spec to be deterministic, so that I more easily can check for unexpected changes.
As a workaround, I have added a document processor:
config.DocumentProcessors.Add(new SortKeysDocumentProcessor());
The text was updated successfully, but these errors were encountered: