getRedirectionURL doesn't seem to trigger

here's part of my backendConfig: (need to break up for character limit)

EmailPasswordNode.init({ signUpFeature: { formFields: [{ id: "name" }, { id: "company", optional: true }] }, signInAndUpFeature: { defaultToSignUp: true },

getRedirectionURL: async (context) => { if (context.action === "RESET_PASSWORD") { // called when the user clicked on the forgot password button } else if (context.action === "SUCCESS") { // called on a successful sign in / up. Where should the user go next? console.log("Context.action is SUCCESS"); let redirectToPath = context.redirectToPath; console.log("redirectToPath is: " + redirectToPath); // if (redirectToPath !== undefined) { // // we are navigating back to where the user was before they authenticated // return redirectToPath; // } if (context.isNewUser) { // user signed up return "/onboarding" } else { // user signed in return "/dashboard" } } // return undefined to let the default behaviour play out return undefined; },

override: { apis: (originalImplementation) => { return { ...originalImplementation, signUpPOST: async function (input) { if (originalImplementation.signUpPOST === undefined) { throw Error("Should never come here"); } // First we call the original implementation of signUpPOST. let response = await originalImplementation.signUpPOST(input); // Post sign up response, we check if it was successful if (response.status === "OK") { // These are the input form fields values that the user used while signing up let formFields = input.formFields; // console.log("signup form fields:"); var name = formFields.find(i => i.id === "name").value; var userId = response.user.id; var returnObject = { didWork: false, error: "" }; //db calls hidden here } return response; } } } }

The

getRedirectionURL

goes on the frontend

If you see the titles of the code snippets on the link above,

getRedirectionURL

is used under react, angular and vue code tabs

I'm building off of the NextJS sample, which has a frontendConfig and a backendConfig file, but they look very similar, so it's easy to mix up where something goes

ANy ideas on how we can make it obvious? We had earlier tried to do it based on comments in the code, but people missed that too..

like a line at the top of the code:

// this is on the frontend

I was kind of expecting to see this above every code box

Just a big title saying front end or back end

Since I'm not as familiar with how SuperTokens works yet, what's in front vs back, and auth is something that is just confusing by default and makes your eyes and brain glaze over

even though I can step back and say, wait you are sending a response something works, of course I need to redirect on the front end based on the result, I don't think I can just send a response back with the URL I want and have it magically work, but then again I'm not 100% sure what is catching my code on the front and what it's doing, so...

There's definitely some good examples in your docs, but it can be unclear to figure out where some stuff goes if you aren't super familiar with it yet, and I know you guys would know it in-and-out and it may be harder to step back and see how the rest of us can struggle understanding how it's all put together