You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've identified the reasons to capture analytics in the style guide, however there are a lot of ways to do this poorly, we need to outline what the recommended method is for adding analytics to design system components at Thinkmill, this might include answers to the following questions:
Is React.Context the best place to propagate analytics events? Why?
If yes, what is the best method for exposing this context to all our components
If no, what alternative mechanism should we use and why?
Should there be an analytics package, if yes what should it contain?
What patterns do we leverage to effectively propagate events for each component in their differeing usage contexts?
The text was updated successfully, but these errors were encountered:
We've identified the reasons to capture analytics in the style guide, however there are a lot of ways to do this poorly, we need to outline what the recommended method is for adding analytics to design system components at Thinkmill, this might include answers to the following questions:
The text was updated successfully, but these errors were encountered: