-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
fix: issue-5850 - Settle override conflicts between edges and propagate changes #8089
base: latest
Are you sure you want to change the base?
Conversation
@AlonNavon 🎉 🕺 |
Thank you @owlstronaut! |
@jdalton Yep, working on it! I'm brand new to the team/space, so I'm just starting to learn all about this. Happy to accept any help and direction 😄 Going will be slow 😆 |
// rawSpec can be undefined, so we need to use the fallback value of spec if it is. | ||
let spec = npa(`${edge.name}@${edge.rawSpec || edge.spec}`) |
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.
I'm making an assumption here that we can fallback
…D' for edge override set inconsistencies
@@ -2932,7 +3018,7 @@ t.test('overrides', (t) => { | |||
], | |||
}) | |||
|
|||
t.equal(original.canReplaceWith(badReplacement), false, 'different overrides fails') | |||
t.equal(original.canReplaceWith(equivalentReplacement), true, 'different overrides passes') |
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.
behavior change, equivalent can now override
@jdalton I'm feeling pretty good about this. Any chance you guys have some capacity to take a look? |
This PR is to help get #7025 over the line. The community member did a great job the fixes in - this'll be an attempt to get it over the line
References
Related:
#7025 #5850