fix(scopes): Correctly merge full scopes if multiple operations with the same path belong to different scopes#224
Merged
nickvergessen merged 1 commit intomainfrom Mar 10, 2025
Conversation
…the same path belong to different scopes Signed-off-by: provokateurin <kate@provokateurin.de>
nickvergessen
approved these changes
Mar 10, 2025
Member
|
Thanks for fixing! |
Member
Author
|
Yes, will do right away 👍 |
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
2 participants
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 #222
The array_merge was overwriting existing operations if they had the same path and belonged to different scopes.
Check the spreed changes to see the impact and that it fixes the originally reported issue.