PubSub / Events

[sdn90]

I noticed that some of the components implement a PubSub pattern.

I 100% agree with this personally and think it needs to be used a lot more. It drastically simplifies analytics related code and tests

• Can you expand on your thinking for this?
• Any lessons learned?
• Think it's worth building some conventions around this?

[t-kelly]

💯 We need docs on this

discussion-18.mp4

[leighs-hammer]

Absolutely love this 🙌 need to dig in a bit on the on the implementation to see under the hood 🙈 The use of custom events to pub/sub events within the current pages context is the way forward and has been well been battle tested!!

@t-kelly have you looked at extending this at all to allow these events for cross tab or other state like changes. Example: a customer browsing in one tab opens another tab of a second product they like. They add one product to a cart, emitting an atc event, and updating cart state, not only is subscribed to on the current page but also utilizes session storage or similar flow to update this dynamically accross tabs? Reflecting critical e-commerce state changes to all pages in realtime?

I k ow the previous event engine I built out we had a subscribe to data attribute that would reduce unnecessary state like requests on view changes.