Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix issue with reused blockers on subsequent navigations #10656

Merged
merged 3 commits into from
Jun 30, 2023
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .changeset/fix-reused-blocker.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
---
"react-router": patch
"@remix-run/router": patch
---

Fix issue with reused blockers on subsequent navigations
71 changes: 71 additions & 0 deletions packages/react-router-dom/__tests__/use-blocker-test.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -158,6 +158,77 @@ describe("navigation blocking with useBlocker", () => {
act(() => root.unmount());
});

it("handles reused blocker in a layout route", async () => {
router = createMemoryRouter([
{
Component() {
let blocker = useBlocker(true);
return (
<div>
<Link to="/one">/one</Link>
<Link to="/two">/two</Link>
<Outlet />
<p>{blocker.state}</p>
{blocker.state === "blocked" ? (
<button onClick={() => blocker.proceed?.()}>Proceed</button>
) : null}
</div>
);
},
children: [
{
path: "/",
element: <h1>Home</h1>,
},
{
path: "/one",
element: <h1>One</h1>,
},
{
path: "/two",
element: <h1>Two</h1>,
},
],
},
]);

act(() => {
root = ReactDOM.createRoot(node);
root.render(<RouterProvider router={router} />);
});

// Start on /
expect(node.querySelector("h1")?.textContent).toBe("Home");
expect(node.querySelector("p")?.textContent).toBe("unblocked");
expect(node.querySelector("button")).toBeNull();

// Blocked navigation to /one
act(() => click(node.querySelector("a[href='/one']")));
expect(node.querySelector("h1")?.textContent).toBe("Home");
expect(node.querySelector("p")?.textContent).toBe("blocked");
expect(node.querySelector("button")?.textContent).toBe("Proceed");

// Proceed to /one
act(() => click(node.querySelector("button")));
expect(node.querySelector("h1")?.textContent).toBe("One");
expect(node.querySelector("p")?.textContent).toBe("unblocked");
expect(node.querySelector("button")).toBeNull();

// Blocked navigation to /two
act(() => click(node.querySelector("a[href='/two']")));
expect(node.querySelector("h1")?.textContent).toBe("One");
expect(node.querySelector("p")?.textContent).toBe("blocked");
expect(node.querySelector("button")?.textContent).toBe("Proceed");

// Proceed to /two
act(() => click(node.querySelector("button")));
expect(node.querySelector("h1")?.textContent).toBe("Two");
expect(node.querySelector("p")?.textContent).toBe("unblocked");
expect(node.querySelector("button")).toBeNull();

act(() => root.unmount());
});

describe("on <Link> navigation", () => {
describe("blocker returns false", () => {
beforeEach(() => {
Expand Down
9 changes: 4 additions & 5 deletions packages/react-router/lib/hooks.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -939,7 +939,6 @@ export function useBlocker(shouldBlock: boolean | BlockerFunction): Blocker {
let state = useDataRouterState(DataRouterStateHook.UseBlocker);

let [blockerKey, setBlockerKey] = React.useState("");
let [blocker, setBlocker] = React.useState<Blocker>(IDLE_BLOCKER);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per remix-run/remix#6704 (comment), it was pointed out that we don't even need the blocker in local state anymore. We prefer the state.blockers value anyway as the source of truth that updates via DataRouterStateContext and we can just fallback on IDLE_BLOCKER instead of syncing router state into local state.

let blockerFunction = React.useCallback<BlockerFunction>(
(arg) => {
if (typeof shouldBlock !== "function") {
Expand Down Expand Up @@ -986,15 +985,15 @@ export function useBlocker(shouldBlock: boolean | BlockerFunction): Blocker {
// key of "". Until then we just have the IDLE_BLOCKER.
React.useEffect(() => {
if (blockerKey !== "") {
setBlocker(router.getBlocker(blockerKey, blockerFunction));
router.getBlocker(blockerKey, blockerFunction);
}
}, [router, blockerKey, blockerFunction]);

// Prefer the blocker from state since DataRouterContext is memoized so this
// ensures we update on blocker state updates
// Prefer the blocker from `state` since not `router.state` DataRouterContext
// is memoized so this ensures we update on blocker state updates
return blockerKey && state.blockers.has(blockerKey)
? state.blockers.get(blockerKey)!
: blocker;
: IDLE_BLOCKER;
}

/**
Expand Down
7 changes: 5 additions & 2 deletions packages/router/router.ts
Original file line number Diff line number Diff line change
Expand Up @@ -1026,8 +1026,11 @@ export function createRouter(init: RouterInit): Router {

// On a successful navigation we can assume we got through all blockers
// so we can start fresh
let blockers = new Map();
blockerFunctions.clear();
let blockers = state.blockers;
if (blockers.size > 0) {
blockers = new Map(blockers);
blockers.forEach((_, k) => blockers.set(k, IDLE_BLOCKER));
}
Comment on lines +1029 to +1033
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deleting the blockers here was incorrect if they existed in a reused layout route. Instead we just want to set them back to IDLE_BLOCKER and let the useBlocker useEffect handle deletion on unmount


// Always respect the user flag. Otherwise don't reset on mutation
// submission navigations unless they redirect
Expand Down