Add reset function to useFetcher object to support modal usage

[cblauvelt]

I am using useFetcher to submit form data without navigation within a modal. When a user submits data within the modal and closes the modal I would like clear the fetcher state so when the user re-opens the modal they get the same experience as the first usage.

I can work around this by rendering the modal only when needed which mounts and unmounts the modal component but this seems sub-optimal. Ex:

{modalOpen ? (<ModalComponent />) : null }

See discussion at remix-run/remix#2749.

[brophdawg11]

Yep - I'm on board. @jacob-ebey and I actually almost shipped this as part of v7 so we can dust that off. At the time we were (probably needlessly) waffling on whether we needed reset or abort or both etc.

Let's just ship fetcher.reset() which will abort any in-flight calls. If a standalone abort mechanism ever becomes super necessary we can revisit fetcher.abort. But in the meantime they can accomplish that with fetcher.reset and syncing state.

[jacob-ebey]

👍

[cblauvelt]

Sounds great. Will this issue show when it's merged into main or a development branch?

[brophdawg11]

Not here automatically - you can follow #14207. We usually try to add a comment on the discussion manually but the issue will be the most reliable thing to track.

[brophdawg11]

Issue: #14207
PR: #14206