Skip to content

refactor how we use the redirectTo param#804

Open
gudnuf wants to merge 1 commit intomasterfrom
overhaul-redirect-param-usage
Open

refactor how we use the redirectTo param#804
gudnuf wants to merge 1 commit intomasterfrom
overhaul-redirect-param-usage

Conversation

@gudnuf
Copy link
Contributor

@gudnuf gudnuf commented Jan 30, 2026

There's two approaches in here, one for receive and the other for send and everything else (see note below so we can discuss)

In this PR I made a useRedirectTo hook that handles maintaining the redirectTo query param and also helps us build the route we are navigating to while maintaining search params.

NOTE: I noticed that I had to chase down all of the navigation through out the send and receive flows to make this change, so I introduced a top level receive flow that defines all of the navigation and actions. Let me know what you think @jbojcic1... should I just do it like the send flow or is this type of thing that I added to receive something we should do for send too.

@gudnuf gudnuf requested a review from jbojcic1 January 30, 2026 22:09
@supabase
Copy link

supabase bot commented Jan 30, 2026

This pull request has been ignored for the connected project hrebgkfhjpkbxpztqqke because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@vercel
Copy link

vercel bot commented Jan 30, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
agicash Ready Ready Preview, Comment Jan 30, 2026 10:09pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant