#5004 Maintain consistent element order in exports#5791
Open
rogin wants to merge 1 commit intonextgenhealthcare:developmentfrom
Open
#5004 Maintain consistent element order in exports#5791rogin wants to merge 1 commit intonextgenhealthcare:developmentfrom
rogin wants to merge 1 commit intonextgenhealthcare:developmentfrom
Conversation
Contributor
|
Fixes #5004 |
Contributor
|
My testing notes: A quick peek shows that channel IDs are ordered: I created a channel and changed code template scopes, dependencies, enabled/disabled channels. A diff between server exports after these changes is MUCH easier to read: |
|
I would also like to see this PR merged. The issue this PR solves creates a lot of unnecessary noise versioning systems. |
|
Just letting everyone know that this PR went into BridgeLink 4.5.4. |
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.
Initial testing by @jonbartels showed promise. Should be unit testable, but none provided.