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
{{ message }}
This repository has been archived by the owner on Jun 5, 2024. It is now read-only.
Currently, we are exporting a whole sdk as one single export and then use it globally in the web app. This leads to a need of passing around the sdk context between different parts which haven't got the access to it. A perfect example of this is the store. This is a bit tedious and it would be great if we could import the required modules directly when needed.
The text was updated successfully, but these errors were encountered:
Another advantage we could get with this would be tree shaking. It would probably require a different approach to storing some of the values in helpers. Maybe in a window object? Thoughts @kulmann@fschade ?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, we are exporting a whole sdk as one single export and then use it globally in the web app. This leads to a need of passing around the sdk context between different parts which haven't got the access to it. A perfect example of this is the store. This is a bit tedious and it would be great if we could import the required modules directly when needed.
The text was updated successfully, but these errors were encountered: