-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
fix(core): Fix integration deduping #5696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
b8e9fa8
make deduping consider origin (default vs user-provided), prefer last
lobsterkatie 249d983
apply deduping after combining default and user-provided integrations
lobsterkatie 527da0f
add tag to differentiate integration instances in tests
lobsterkatie e07bb14
add new tests
lobsterkatie af1e60b
remove bogus test
lobsterkatie File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically? Yes. But I'd argue that
a) it falls under the heading of "fixing bugs is always technically breaking", and
b) coming back to the examples from the description, we have
[UserProvidedCopyofIntegration, DefaultCopyOfSameIntegration]
- the user's copy should win, and already does (no behavior change here)[DefaultCopyofIntegration, UserProvidedCopyOfSameIntegration]
- the user's copy should win, but currently doesn't (this seems wrong on its face and also, why would anyone rely on us ignoring their copy?)[DefaultCopyAofIntegration, DefaultCopyBofIntegration]
- copy B should win, but currently doesn't (we have total control here, though I don't think it actually comes up anywhere)[UserCopyAofIntegration, UserCopyBofIntegration]
- copy B should win, but currently doesn't (the one breaking, not-currently-quite-as-obviously-wrong change, but I'm wagering that the number of people actively providing two copies of the same integration is vanishingly small)I honestly have no idea why we were preferring first to begin with (the PR which introduced both the logic and the test unfortunately says absolutely nothing about it), and I can't find any place where we rely on that behavior, so I feel okay changing it.
WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lol at the xkcd
I am totally fine with the changes. If people report in that they see problems, we can tell them to change the order to match the fixed behavior!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whoops - completely forgot to include your good suggestion above before I merged. I'll throw it into the pile for the next comments-fix PR.