fix(s2): prevent infinite render loop in Tabs inside DropZone#10090
Open
reidbarber wants to merge 2 commits into
Open
fix(s2): prevent infinite render loop in Tabs inside DropZone#10090reidbarber wants to merge 2 commits into
reidbarber wants to merge 2 commits into
Conversation
|
Build successful! 🎉 |
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.
Closes #10057
Updates S2 Tab to derive contentId from a baseId shared on InternalTabsContext plus the tab's id, so independent CollectionBuilder portals produce the same value and mergeIds doesn't infinitely oscillate between values.
✅ Pull Request Checklist:
📝 Test Instructions:
Unit test should cover. Just smoke test S2 Tabs.
🧢 Your Project: