Fix #47. Sort paths and components for deterministic specification #49
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
There is non-deterministic output of the generation of the OpenAPI 3.0 document produced by this plugin. Also see #47.
When the file is committed to a source code repository, this causes a diff without changing the actual content of the specification.
The sorting is done by a specialized class, which may be removed after this has been fixed in
swagger-core
.This PR
paths
components
:Schemas
(recursively)Responses
Parameters
Examples
RequestBodies
Headers
SecuritySchemes
Links
Callbacks
Extensions
This should solve the problem.
References to other issues and pull requests in Swagger Core: