Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add invocation event information to verifyUserEmails parameters #9505

Open
mtrezza opened this issue Dec 24, 2024 · 1 comment
Open

Add invocation event information to verifyUserEmails parameters #9505

mtrezza opened this issue Dec 24, 2024 · 1 comment
Labels
bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature

Comments

@mtrezza
Copy link
Member

mtrezza commented Dec 24, 2024

New Feature / Enhancement Checklist

Current Limitation

When setting the Parse Server option verifyUserEmails to a function, it's unknown to the function why it has been called. This does not allow for taking specific action according to the event.

Feature / Enhancement Description

Add a parameter to the method call, to know whether:

  • It was a sign-up or login
  • Which auth method has been used (username/password, auth provider)

It could simply pass the object that would be stored in the session createdWith field, as that already contains all the infos, for example:

{ "action": "login", "authProvider": "apple" }
{ "action": "signup", "authProvider": "password"}

Example Use Case

Require email verification only for auth providers who do not verify email addresses themselves.

Copy link

Thanks for opening this issue!

  • 🎉 We are excited about your ideas for improvement!

@mtrezza mtrezza added bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature labels Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature
Projects
None yet
Development

No branches or pull requests

1 participant