Fixes #2598 - implements forced sort order. #2601
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
The idea of the decoupler count was not implemented. It just does a parent part count instead. Trying to decide what counts as a decoupler is messy, and it wasn't easy to borrow the PART:DECOUPLER logic, because that's too tied to our PartValue wrapper around the part, and this is happening at a more low-level than that.
Dunbaratu
added
enhancement
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.
The idea of the decoupler count was not implemented.
It just does a parent part count instead. Trying to
decide what counts as a decoupler is messy, and it
wasn't easy to borrow the PART:DECOUPLER logic,
because that's too tied to our PartValue wrapper
around the part, and this is happening at a more
low-level than that.