LWCIntermediatewireperformancereactivity
Optimize re-render storm from @wire reactive parameter object literal
Real World Scenario
List LWC causes 200+ getRecords network calls per minute; developer passed new object literal as wire parameter each render cycle.
Expected Answer
• Wire parameters must be primitives or stable object references
• Build filter object in getter returning same reference when values unchanged
• Or split into multiple primitive wire parameters
• Use @wire with $property reactive pattern correctly — avoid inline {} in template
• Chrome network tab to count duplicate requests during scroll
• Consider imperative fetch debounced for complex dynamic filters
• Document wire reactivity rules in team LWC standards
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Wire parameters must be primitives or stable object references Also consider: Build filter object in getter returning same reference when values unchanged In practice: Or split into multiple primitive wire parameters Balance speed of delivery with maintainability.
Architect Perspective
Object literal wire params are the #1 accidental DDoS of your own Apex — catch in code review.