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
Right now a lot of the apps we have contain hardcoded event names in order to send messages to different apps so that each app's state can be updated accordingly. The AvMessage package is simple for dispatching events to the browser and it would be nice to do, one or both of the following options:
1 - Create Pre-defined set of event names that we have considered to use for our apps. By doing this we can have a better understanding of all the values we are passing around all these apps.
Ex:
// Constants is an export from `avMessages`avMessages.subscribe(Constants.FAVORITES_UPDATED,(favorites)=>{// Update your favorites inside your component});
2 - Create a package containing methods that already have these pre-defined event names filled in and formats the data returned easily for both sending and receiving updates.
Ex:
avMessages.onFavoritesUpdated((favorites)=>{// Update your favorites inside your component});
With either decision we can at least include a readme of what we are expected to send/receive with each of the pre-defined values. It is also possible that we ditch this strategy and identify all the components this package has to live in and just create react components out of them so the users don't have to worry about implementing this.
The text was updated successfully, but these errors were encountered:
Right now a lot of the apps we have contain hardcoded event names in order to send messages to different apps so that each app's state can be updated accordingly. The
AvMessage
package is simple fordispatching
events to the browser and it would be nice to do, one or both of the following options:1 - Create Pre-defined set of event names that we have considered to use for our apps. By doing this we can have a better understanding of all the values we are passing around all these apps.
Ex:
2 - Create a package containing methods that already have these pre-defined event names filled in and formats the data returned easily for both sending and receiving updates.
Ex:
With either decision we can at least include a readme of what we are expected to send/receive with each of the pre-defined values. It is also possible that we ditch this strategy and identify all the components this package has to live in and just create
react
components out of them so the users don't have to worry about implementing this.The text was updated successfully, but these errors were encountered: