infinite loop fix in any collection page#1615
Conversation
Signed-off-by: ragnep <ragneinfo@gmail.com>
WalkthroughMoved conditional clearing of query parameters from query parsing to navigation handling and narrowed a component useEffect dependency to only depend on resolved account address. No exported APIs changed. Changes
Sequence Diagram(s)sequenceDiagram
participant UI
participant Router
participant PageClient as page.client.tsx
participant Component as CollectionDelegation
UI->>Router: navigate(to section)
Router->>PageClient: updatePath(newSection)
alt newSection is CHECKER or ASSIGN_PRIMARY_ADDRESS
PageClient-->>PageClient: keep addressQuery
else
PageClient-->>PageClient: clear addressQuery
end
alt newSection is REGISTER_DELEGATION
PageClient-->>PageClient: keep collectionQuery / useCaseQuery
else
PageClient-->>PageClient: clear collectionQuery / useCaseQuery
end
PageClient->>Component: render with updated queries
Component-->>Component: useEffect triggered on accountResolution.address only
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes
Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|



Summary by CodeRabbit
Bug Fixes
Performance
✏️ Tip: You can customize this high-level summary in your review settings.