Open Andreas-Hjortland opened 1 month ago
I cannot fix this until we have updated minimum required version to angular 18, until then the workaround will be to use module based providers or add the plugin in the root of the app, and let any child pages be bootstrapped individually instead of as angular routes.
Also depends on this fix https://github.com/ngxs/store/issues/2227
Describe the bug Because we are adding the plugin using the
NGXS_PLUGINS
injection token instead of thewithNgxsPlugin
, we cannot load the plugin on a lazy loaded route, but have to do it in the entry point (where we callprovideStore
.To Reproduce
provideStores
and add the plugin withwithNgxsMessagePlugin
Expected behavior Expected the state to change when the child handler receives the events from the parent handler.
Desktop (please complete the following information):