parse-community / parse-community/parse-server
Pairing session with installation when using GraphQL
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
The REST API have an option to pair session with installation but it looks like there's no alternative out of box for the GraphQL.
Feature / Enhancement Description
It would be great if there's similar API using the GraphQL and out of the box pair session with installation on the Parse Server. If is out of the box feature this will eliminate the need to do some calls using master key as the session or the installation permissions can differ.
If there's chance the GraphQL API to respect x-parse-installation-id will be great.
Example Use Case
Example 1: me GraphQL query or mutation which respect x-parse-installation-id header.
Example 2: login, signUp respecting x-parse-installation-id header
Alternatives / Workarounds
- creating and saving an installation
- creating a session using login, signUp etc.
- update session's installationId
3rd Party References
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the REST API's session-installation pairing with the GraphQL entry points named in the issue: me, login, and signUp. Investigate how GraphQL handles the x-parse-installation-id header and session permissions. Done means GraphQL provides equivalent pairing behavior or consistently respects the header without requiring a master-key session.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, javascript, nodejs
- Domain
- api, authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100