You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to see what is capable with the next() function besides bubbling errors to a Stormpath form. More specifically I want to not only send a new Error to the form from an express preRegistrationHandler (which I know how to do because it is in the documentation), but I also want to fire a function within scope of the form from the preRegistrationHandler.
Now I know that there is a next() call in my client-side onFormSubmit which then passes data to the preRegistrationHandler in express, but how can I access the scope of the form again from the preRegistrationHandler? I am unsure if I should be passing a function or some type of callback into the client-side next() prior to the preRegistrationHandler.
The text was updated successfully, but these errors were encountered:
Hi @dylanfpaul , thanks for the question. I'm no sure what you mean by the scope of the form? If you could describe the user story you're trying to achieve, that may help. Also, please make sure to read the announcement that Stormpath is Joining Okta if you haven't already. Thanks!
I want to see what is capable with the next() function besides bubbling errors to a Stormpath form. More specifically I want to not only send a new Error to the form from an express preRegistrationHandler (which I know how to do because it is in the documentation), but I also want to fire a function within scope of the form from the preRegistrationHandler.
Now I know that there is a next() call in my client-side onFormSubmit which then passes data to the preRegistrationHandler in express, but how can I access the scope of the form again from the preRegistrationHandler? I am unsure if I should be passing a function or some type of callback into the client-side next() prior to the preRegistrationHandler.
The text was updated successfully, but these errors were encountered: