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.

Sign up for GitHub

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

Jump to bottom

Working with SingleFetch (Remix v2.9.0) #17

Open
GuptaSiddhant opened this issue May 16, 2024 · 0 comments · May be fixed by #18
Open

Working with SingleFetch (Remix v2.9.0) #17

GuptaSiddhant opened this issue May 16, 2024 · 0 comments · May be fixed by #18

Comments

@GuptaSiddhant
Copy link

Currently remix-toast heavily depends on json and redirect response utilities. With the new SingleFetch, Remix recommends moving away from response utils and start using the ResponseStub.

What would be the correct path to update the usage of remix-toasts to new singleFetch? Would the API need a change to accept the ResponseStub?
@GuptaSiddhant GuptaSiddhant linked a pull request May 16, 2024 that will close this issue
Open
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: update to work with single fetch responseStub GuptaSiddhant/remix-toast
1 participant
@GuptaSiddhant