Optimize the composer properties sorting #73
Merged
Conversation
This file contains 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
kayw-geek
force-pushed
the
feature/normalize-composer-file
branch
from
e392d43 to
4e27d48
Compare
kayw-geek
force-pushed
the
feature/normalize-composer-file
branch
from
4e27d48 to
5719616
Compare
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.
Summary
This PR optimizes the sorting of Composer properties according to the schema provided by the official documentation.
Details
Optimization: The sorting of Composer properties has been optimized to follow the official schema. This ensures that the properties are displayed in a consistent and predictable order.
Implementation: The ordering logic has been updated to reference the official schema, providing a more robust and reliable method for sorting Composer properties.