Fix updating with fragments ignoring original profile settings#9293
Conversation
| auto childImpl{ matchingProfile->CreateChild() }; | ||
| childImpl->LayerJson(profileStub); | ||
| childImpl->Origin(OriginTag::Fragment); | ||
| childImpl->Source(source); |
There was a problem hiding this comment.
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
carlos-zamora
left a comment
There was a problem hiding this comment.
Wait. I'm pretty sure I introduced this for SUI Inheritance. So this'll probably break the tooltip there.
Blocking while I look into this a bit more.
Lol I just commented on that PR (#9079) asking if we need this call |
carlos-zamora
left a comment
There was a problem hiding this comment.
Tested with SUI Inheritance. Adding the source there wasn't necessary. My bet is that I was using the source to handle fragment-extensions like dynamic profiles, then I added OriginTag::Fragment to not have to do that (and look at the source), and just never removed that source call.
|
@msftbot merge this in 1 minute |
|
Hello @DHowett! Because you've given me some instructions on how to help merge this pull request, I'll be modifying my merge approach. Here's how I understand your requirements for merging this pull request:
If this doesn't seem right to you, you can tell me to cancel these instructions and use the auto-merge policy that has been configured for this repository. Try telling me "forget everything I just told you". |
Turns out we were adding the fragment source to profiles we update. This
PR fixes it so we keep the original source.
Validation Steps Performed
Existing profile settings are maintained
Closes #9290