parse-community / parse-community/parse-dashboard
Inconsistent internal server app identification
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest versions of Parse Server and Parse Dashboard.
Issue Description
As described in https://github.com/parse-community/parse-dashboard/pull/2627#issuecomment-2562944934, the internal identification of an app is not well implemented in the sense that:
- it's not unique across features, e.g. scripts
- it imposes restrictions on app names (no duplicates)
- it's not clearly documented
Suggested Solution
Review this identification logic, unify it across the features in the dashboard (scripts, info panel, etc) and document any restrictions (e.g. no duplicate app names, etc) for the dashboard user.
Environment
Dashboard
- Parse Dashboard version:
6.0.0
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 reviewing the discussion in parse-dashboard#2627 and tracing the current app-identification logic across the scripts and info panel features. Document the restrictions users must follow, including duplicate app-name behavior, and consider the work done when identification is unified across the mentioned features and its rules are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation, frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100