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
Parse Server SDK Javascript offers support for passing context with the save, login (and perhaps signUp) methods.
This has permitted my team to easily implement custom OTP signing flows with our web apps.
It will be nice if we can do same from our flutter app.
Feature / Enhancement Description
The feature request is simply to allow ParseUser class save, login, and signUp methods to be able to take context object that will be sent to the backend very similar to how the JS SDK does it.
Example Use Case
I want to be able to do the following and have it reflect in the backend for example:
An alternative is to use custom auth provider, however, this approach too comes with a challenge as it does now trigger the afterLogin event after the user successfully logs in.
The text was updated successfully, but these errors were encountered:
🎉 We are excited about your ideas for improvement!
mtrezza
changed the title
Will be nice to have ParseUser save, signUp and login methods with fully supported context.
Support context for ParseUser save, signUp and login methods
Oct 3, 2024
mtrezza
changed the title
Support context for ParseUser save, signUp and login methods
Support context for Parse.User save, signUp and login methods
Oct 3, 2024
New Feature / Enhancement Checklist
Current Limitation
Parse Server SDK Javascript offers support for passing context with the save, login (and perhaps signUp) methods.
This has permitted my team to easily implement custom OTP signing flows with our web apps.
It will be nice if we can do same from our flutter app.
Feature / Enhancement Description
The feature request is simply to allow ParseUser class save, login, and signUp methods to be able to take context object that will be sent to the backend very similar to how the JS SDK does it.
Example Use Case
I want to be able to do the following and have it reflect in the backend for example:
Alternatives / Workarounds
An alternative is to use custom auth provider, however, this approach too comes with a challenge as it does now trigger the afterLogin event after the user successfully logs in.
The text was updated successfully, but these errors were encountered: