What about complex alerts (like a popup)? about flux

[fisherwebdev]

A lot of this seems very specific to your application, and it's difficult to get enough context from what you have written here. Perhaps more code would help the community here understand your issue?

But on a side note, this concerns me:

alertStore.add({contents: new UnlockJob({...})})

That looks an awful lot like a setter on your store, and a store should not have any setter methods. The only way data should be getting into the store is though the callback it registers with the dispatcher.

[totty90]

A lot of this seems very specific to your application, and it's difficult to get enough context from what you have written here. Perhaps more code would help the community here understand your issue?

Imagine a popup, where would you store in your app?

[fisherwebdev]

I would render a PopupControllerView at the bottom of the body, in it's own React root, which would be listening to stores. It might have number of child popups, or I might create logic to dynamically create those children.

I might maintain a PopupStore, which would have currentPopupID value, which could be null. Down in my list of popup components, they would all receive currentPopupID as a prop, and if their popupID matched, they would get displayed.

Or I would simply let the values in the other stores drive what popup to render more directly, perhaps with some logic in PopupControllerView determining if a popup should be displayed, or which one.

Basically this is all just Flux + React -- nothing special going on, other than creating a separate root for it, and I'm not even sure that's necessary. The generic Popup React component could be made to simply take props and let the store or controller-view above it determine those props. You could then use that generic component to compose various different popups.