parse-community / parse-community/docs

📙 Anonymous users ID ?

Open
#842 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type:docs
Dominant language
SCSS
Stars
317
Forks
507
PR merge metrics
No merged PRs in 30d

Description

Link to section:
Please provide a specific link to the section in question. In the docs, you can click on a heading and then copy the relative link from the address bar.
https://docs.parseplatform.org/parse-server/guide/#anonymous-user-authdata

What is the issue?
Please provide a detailed explanation of the problem, quoting parts of the docs or using screenshots if appropriate.

More details on the use of this ID should be added.

  • Do we need to secure (keep secret) this ID?
  • Is it used as a seed, does it need to remain constant ?

Looking at the code, it doesn't seems to be used anywhere else than in tests.

https://github.com/parse-community/parse-server/search?p=2&q=anonymous

Can you propose a solution?
What changes do you think should be made? Have you considered multiple solutions? Will this be suitable for all use cases?

Add something like :

The ID is used for XYZ and need to XYZ.

Contributor guide

No contributing guide indexed for this repository

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 with the Parse Server Guide section at https://docs.parseplatform.org/parse-server/guide/#anonymous-user-authdata and review the linked anonymous-user search results. Determine from the documentation and referenced tests whether the anonymous user ID must be secret or stable, then update that section with the confirmed explanation and verify that it answers both questions.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.