Uh oh!
There was an error while loading. Please reload this page.
Fix invariant violation when nesting VirtualizedList inside ListEmptyComponent - #35875
Closed
NickGerleman wants to merge 1 commit into
Closed
Fix invariant violation when nesting VirtualizedList inside ListEmptyComponent#35875NickGerleman wants to merge 1 commit into
NickGerleman wants to merge 1 commit into
Conversation
facebook-github-bot
commented
Jan 18, 2023
Contributor
This pull request was exported from Phabricator. Differential Revision: D42574462 |
facebook-github-bot
commented
Jan 18, 2023
Contributor
This pull request was exported from Phabricator. Differential Revision: D42574462 |
NickGerlemanforce-pushed
the
export-D42574462
branch
from
January 18, 2023 14:05
1f5f284 to
5efb813CompareNickGerlemanforce-pushed
the
export-D42574462
branch
from
January 18, 2023 14:12
5efb813 to
615dcfdComparefacebook-github-bot
commented
Jan 18, 2023
Contributor
This pull request was exported from Phabricator. Differential Revision: D42574462 |
…Component (react#35875) Summary: Pull Request resolved: react#35875Fixesreact#35871 Nested VirtualizedLists register to their parents for updates, associated to a specfific cellKey set by VirtualizedListCellContextProvider. This cellKey is usually set when rendering a cell for a data item, but we can also render a nested VirtualizedList by putting one in a ListHeaderComponent/ListFooterComponent/ListEmptyComponent. D6603342 (react@a010a0c) added cellKeys when we render from a header/footer, but not ListEmptyComponent, so that association would silently fail earlier. D39466677 (react@010da67) added extra invariants to child list handling, that are now triggered by this case, complaining because we are trying to unregister a child list we never successfully registered, due to a missing cellKey. This fixes the issue by providing a cellKey for ListEmptyComponent as well. Changelog: [General][Fixed] - Fix invariant violation when nesting VirtualizedList inside ListEmptyComponent Differential Revision: D42574462 fbshipit-source-id: 99b51f891737eeb8b3b58b94aa6d4fd04a35d12d
NickGerlemanforce-pushed
the
export-D42574462
branch
from
January 18, 2023 14:25
615dcfd to
be8524bComparefacebook-github-bot
commented
Jan 18, 2023
Contributor
This pull request was exported from Phabricator. Differential Revision: D42574462 |
analysis-bot
commented
Jan 18, 2023
Base commit: 473eb1d |
facebook-github-bot
commented
Jan 19, 2023
Contributor
This pull request has been merged in 1fef376. |
kelset pushed a commit
that referenced
this pull request
Jan 30, 2023
…Component (#35875) Summary: Pull Request resolved: #35875Fixes#35871 Nested VirtualizedLists register to their parents for updates, associated to a specfific cellKey set by VirtualizedListCellContextProvider. This cellKey is usually set when rendering a cell for a data item, but we can also render a nested VirtualizedList by putting one in a ListHeaderComponent/ListFooterComponent/ListEmptyComponent. D6603342 (a010a0c) added cellKeys when we render from a header/footer, but not ListEmptyComponent, so that association would silently fail earlier. D39466677 (010da67) added extra invariants to child list handling, that are now triggered by this case, complaining because we are trying to unregister a child list we never successfully registered, due to a missing cellKey. This fixes the issue by providing a cellKey for ListEmptyComponent as well. Changelog: [General][Fixed] - Fix invariant violation when nesting VirtualizedList inside ListEmptyComponent Reviewed By: christophpurrer Differential Revision: D42574462 fbshipit-source-id: f76fa795bf471cb8a929c2efdbd814ea51927663 # Conflicts: # Libraries/Lists/VirtualizedList.js
Merged
This was referenced Jan 8, 2024
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Summary:
Fixes#35871
Nested VirtualizedLists register to their parents for updates, associated to a specfific cellKey set by VirtualizedListCellContextProvider. This cellKey is usually set when rendering a cell for a data item, but we can also render a nested VirtualizedList by putting one in a ListHeaderComponent/ListFooterComponent/ListEmptyComponent.
D6603342 (a010a0c) added cellKeys when we render from a header/footer, but not ListEmptyComponent, so that association would silently fail earlier.
D39466677 (010da67) added extra invariants to child list handling, that are now triggered by this case, complaining because we are trying to unregister a child list we never successfully registered, due to a missing cellKey.
This fixes the issue by providing a cellKey for ListEmptyComponent as well. It also cleans up some of the parameterization needed from when we had two VirtualizedList implementations.
Changelog:
[General][Fixed] - Fix invariant violation when nesting VirtualizedList inside ListEmptyComponent
Differential Revision: D42574462