v0.7.5

Two fixes where an action or a watcher silently never happened. Neither changes the API; both change what your app sees in a case that used to fail quietly.

What changes for your app

• A second confirm no longer strands the first. When an action with a confirm was dispatched while another confirmation was still open (from a watch, or a programmatic injectActions().execute()), it replaced the open one, and the first execute() never settled: no onSuccess, no onError, no settled action observer. Now only one confirmation is open at a time, and a new one cancels the waiting one, so its execute() rejects with the usual cancellation (isActionCancelled(error) is true). A late answer to the replaced dialog no longer closes its successor.
• watch fires for writes made on an external store. In controlled mode (the store input), watch only heard about writes made through the renderer. A write from your own state management re-rendered the UI but triggered no watcher. On every store notification the renderer now compares the new snapshot with the last one, by reference, and reports each changed path, containers included (/user as well as /user/name). Writes made through the renderer are still reported once, not twice.

Upgrading

npm i ngx-json-render@^0.7.5

No code changes are needed, and ngx-json-render-material@0.3.6 works with it as it is. If you use an external store, check that it replaces objects on write rather than editing them in place: a store that mutates its snapshot still re-renders, but its changes cannot be seen by the comparison and trigger no watch.

Full Changelog: v0.7.4...v0.7.5