Wondering if anyone has figured out exactly how to replace the Ash Authentication magic link landing page (the one a user gets after clicking their magic link email)?
I found this cryptic note in the Magic Link tutorial:
You probably don’t want to serve this page to users in production. You can work around this by placing your own page at the same path before it in the router, or changing the email link to a different URL.
Unfortunately the “see also” link is pretty useless (no docs there, really), and the MagicSignInLive page and overrides guide don’t really address this specific question.
After perusing the source, it looks like the intention is for me to:
- Write my own
AshAuthentication.Phoenix.MagicSignInLive(which seems pretty straightforward), - And then reuse
AshAuthentication.Phoenix.Components.MagicLink.SignIn(or make something like it) to generate the required interaction button on said page (unless… this is for the sign-in button on the login page… err…, - And somehow inject it into the target landing URL (not clear on how to do that, e.g., “placing your own page at the same path before it in the router, or changing the email link,” but not clear how to do that).
Would be great if someone has done this and could post a little detail so I don’t end up going down the wrong path. 
Ultimately, what I’m after is wrapping the page in my root layout (header, menu, etc.) and put a bit of “Welcome back!” style text on the page.
Ideally… Seems ideal if we had a component that would just render the button, and could add that to any page of our own design. Hm. Well, maybe that’s essentially what I could extract from MagicSignInLive if I can figure it out…
