parse-community / parse-community/parse-dashboard
Add context to dashboard calls
Open
Nobody has claimed this yet.
type:feature
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
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
Parse Dashboard uses the JS SDK with the masterKey. It would be helpful to have context in cloud code whether the masterKey is being used in the dashboard, or via the cloud code.
Feature / Enhancement Description
obj.save(null, { context: {dashboard: true }})
Parse.Cloud.beforeFind('Object', ({ context, master}) => {
if (context.dashboard && master) {
// custom logic for dashboard only
}
});
Example Use Case
Alternatives / Workarounds
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 tracing Parse Dashboard's JavaScript SDK calls that use the masterKey and compare them with the cloud-code context shown in the issue. Determine where dashboard requests would carry the proposed context, then verify that cloud code can distinguish dashboard calls from cloud-code calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100