LWCIntermediatelmscommunicationux
Build LMS-filter-sync pattern for Opportunity pipeline board LWCs
Real World Scenario
Filter panel, kanban board, and totals footer LWCs on same app page drift when user changes owner filter—only board updates.
Expected Answer
• Single LMS channel pipeline_filter_changed with typed payload
• Filter LWC publishes on change; board and footer subscribe
• Initial state: footer reads filter from URL or default on load
• Debounce filter publish 300ms on text input filters
• Unsubscribe disconnectedCallback preventing duplicate handlers
• Payload includes filterVersion increment detecting stale handlers
• Jest test triple component LMS integration with message context
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Single LMS channel pipeline_filter_changed with typed payload. Filter LWC publishes on change; board and footer subscribe. Pick based on your integration pattern and team capability. Filter sync is canonical LMS use case—document payload schema before three teams implement three channels. Balance speed of delivery with maintainability.
Architect Perspective
Filter sync is canonical LMS use case—document payload schema before three teams implement three channels.