feat(poly sync): sort the bricks to add by brick type and alphabetically - #457
Merged
Conversation
|
6 tasks
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
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.



Description
When running
poly sync: sorting the bricks that are missing in thepyproject.tomlfiles.Sorting by brick type, and then alphabetically
first bases, then components.
Comment: the use case for the sync command is mostly to handle missing components, but in cases where there are multible bases, the sorting will handle that too.
Motivation and Context
To improve the developer experience, making the added bricks nicely sorted, for teams that only adds a base to a project, and then relies on the
poly synccommand to add all the needed components.How Has This Been Tested?
✅ CI
✅ added unit tests
Types of changes
Checklist: