š Anonymous users ID ?
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
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.
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.
- Dominant language
- SCSS
- Stars
- 317
- Forks
- 506
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from parse-community/docs
-
šOpendocs:cloud-code type:docs
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
parse-community/docs#936 Ā·
-
type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
parse-community/docs#889 Ā· 7 comments Ā·
-
docs:sdk-js
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
parse-community/docs#961 Ā·
-
type:bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
parse-community/docs#950 Ā· 2 comments Ā·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
parse-community/docs#947 Ā·
All issues in parse-community/docs
Similar issues
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
PedestrianDynamics/pyFDS-Evac#475 Ā·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ethereum/execution-apis#915 Ā·
Maintainers usually reply within 1 day
-
area:ansible source:reader type:content-error
Difficulty 1/5 Under an hour Newbie friendliness 86/100
stephrobert/blog-roadmap#42 Ā·