Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add useMaintenanceKey to query options #2392

Open
3 tasks done
mtrezza opened this issue Dec 24, 2024 · 1 comment
Open
3 tasks done

Add useMaintenanceKey to query options #2392

mtrezza opened this issue Dec 24, 2024 · 1 comment
Labels
bounty:$10 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature

Comments

@mtrezza
Copy link
Member

mtrezza commented Dec 24, 2024

New Feature / Enhancement Checklist

Current Limitation

The maintenanceKey has been introduced in Parse Server and can be used via REST API to access internal fields, but not via the Parse JS SDK.

Feature / Enhancement Description

For use in Cloud Code, Parse.Query should accept an option useMaintenanceKey similar to useMasterKey, to execute the query using the maintenanceKey.

Alternatives / Workarounds

Make a REST API call in Cloud Code.
@parse-github-assistant Parse GitHub Assistant
Copy link

Thanks for opening this issue!

  • 🎉 We are excited about your ideas for improvement!

@mtrezza mtrezza added type:feature New feature or improvement of existing feature bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) bounty:$10 Bounty applies for fixing this issue (Parse Bounty Program) and removed bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) labels Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bounty:$10 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mtrezza