A bit of guidance about freezer HOT 4 CLOSED

Hi @qur2
I am always keen to use reactions. I guess that url changes will update freezer's state, and to update the url you can use actions like:

freezer.trigger('url:go', '/my_path');
freezer.trigger('url:replace', '/my_path');

Inside those actions you can put all the router5 code, and other devs could hook directly into the action to detect url changes.

from freezer.

Thanks for your insight. Also, in redux-router5, they allow to dispatch navigate actions to actually control the router. I'm wondering if that's a good idea for freezer or if I should keep it simple.

By the way: https://www.npmjs.com/package/freezer-js-router5

from freezer.

Regarding triggering, does it make any difference to trigger on the state or from a listener (I assume so)? If so, what would be a a best practice? I assume that triggering on the state makes it easier for the client code since they don't have to get a listener from a node and they be interested only in the events and not the state itself. Does that make sense?

Thanks for your help.

from freezer.

I'm closing this, thanks for your help. I've updated the lib to have reactions as well, but it is opt-in.

from freezer.