parse-community / parse-community/parse-server

GraphQL: verifyEmail with emailed token

Open
#7,028 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type:feature
Dominant language
JavaScript
Stars
21.4k
Forks
4.8k
Avg merge
7h 45m
Merged PRs (30d)
11

Description

New Issue Checklist
Issue Description

This REST endpoint to handle email verification links doesn't seem to have a matching GraphQL mutation

Steps to reproduce

Read the docs, spend a few days getting logins to work using GraphQL.

Actual Outcome

Complete the job with a REST endpoint :-)

Expected Outcome

A complete GraphQL API for managing users, w/o the need for the /parse REST API. Maybe there's a reason for this I don't understand.

Environment

"resolutions": {
"graphql": "^14.7.0"
},
"dependencies": {
"dotenv": "^8.2.0",
"express": "^4.17.1",
"graphql": "^14.7.0",
"graphql-tag": "^2.11.0",
"nodemon": "^2.0.6",
"parse-server": "^4.4.0",
"parse-server-aws-ses": "^1.0.0"
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the REST email-verification endpoint in src/Routers/PublicAPIRouter.js with the user mutations in src/GraphQL/loaders/usersMutations.js. Read the GraphQL documentation and existing mutation patterns, then define the verifyEmail mutation's behavior to match REST verification. Done means users can verify emailed tokens through GraphQL without using the /parse REST API.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, javascript, node.js
Domain
api, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.