OpenAPI module ordering #960
Draft
+10
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…order - Modified copySubProjectsOpenAPIFiles task to sort modules based on the order defined in settings.gradle.kts - Replaced alphabetical ordering with custom sorting that uses rootProject.subprojects order - Unknown modules are placed at the end using Int.MAX_VALUE as sort key - This ensures the generated OpenAPI specification preserves the intended module sequence
jreynard-code
force-pushed
the
swagger-sections-reordering
branch
from
ec40c02 to
b9baef2
Compare
|
need to rethink this as explained by JREY today |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes OpenAPI module ordering to respect settings.gradle.kts include() order, rather than alphabetical order