@magicdoor/magic-use-case-react 0.1.0 → 0.1.1

package/CHANGELOG.md

@@ -1,5 +1,20 @@
 # @magicdoor/magic-use-case-react
 
+## 0.1.1
+
+### Patch Changes
+
+- Close a use case's mutation window on the scope it opened, rather than on
+  whichever scope is current when it finishes.
+
+  A run can outlive the scope it started in — a detached one, or one still in
+  flight when a request ends. Resolving the scope again at closing time made that
+  run decrement a scope it never belonged to, shutting a window another run was
+  depending on: the second run's next write to application state failed with
+  "Cannot set property … outside a use case" even though it was squarely inside
+  `runLogic`. On a server it was worse than a wrong count, since resolving a scope
+  with no request in progress throws, and it threw from inside a `finally`.
+
 ## 0.1.0
 
 ### Minor Changes

package/dist/index.js

@@ -123,21 +123,22 @@ function onNavigation(handler) {
   return () => emitter.unregisterFromNavigation(wrapper);
 }
 function openMutationWindow() {
-  currentScope().openMutationWindows += 1;
-}
-function closeMutationWindow() {
   const scope = currentScope();
+  scope.openMutationWindows += 1;
+  return scope;
+}
+function closeMutationWindow(scope) {
   scope.openMutationWindows = Math.max(0, scope.openMutationWindows - 1);
 }
 function isMutationWindowOpen() {
   return currentScope().openMutationWindows > 0;
 }
 async function withMutationWindow(run) {
-  openMutationWindow();
+  const scope = openMutationWindow();
   try {
     return await run();
   } finally {
-    closeMutationWindow();
+    closeMutationWindow(scope);
   }
 }
 function assertMutationWindowOpen(operation) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@magicdoor/magic-use-case-react",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "React bindings for magic-use-case — clean-architecture use cases and presenters for front-end TypeScript.",
   "type": "module",
   "main": "./dist/index.js",