Fix infinite re-render loop in NameManagerDialog (React #185) - #39
Merged
Merged
Conversation
The namedRanges selector returned a fresh [] on every render when the value was undefined, failing Zustand's Object.is check and looping forever. Use a stable module-level constant instead. Also document the same trap on getPinnedMessages.
Reviewer's guide (collapsed on small PRs)Reviewer's GuideFixes the NameManagerDialog infinite re-render loop by replacing its per-render empty-array fallback with a stable module-level reference, and documents the equivalent Zustand selector pitfall for getPinnedMessages. Sequence diagram for the stable Zustand selector fallbacksequenceDiagram
participant React
participant NameManagerDialog
participant Zustand
React->>NameManagerDialog: render()
NameManagerDialog->>Zustand: useStore(selector)
Zustand-->>NameManagerDialog: workbook.namedRanges or EMPTY_NAMED_RANGES
Zustand->>Zustand: Object.is compares selected reference
alt namedRanges is undefined
Zustand-->>Zustand: Stable EMPTY_NAMED_RANGES reference
else namedRanges exists
Zustand-->>Zustand: Existing namedRanges reference
end
Zustand-->>React: No unnecessary re-render
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Contributor
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Advanced Run ID: Comment |
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.
The namedRanges selector returned a fresh [] on every render when the value was undefined, failing Zustand's Object.is check and looping forever. Use a stable module-level constant instead. Also document the same trap on getPinnedMessages.
Summary by Sourcery
Use a stable fallback for missing named ranges and document safe usage of dynamically allocated selector results.
Bug Fixes: