parse-community / parse-community/parse-server
Allow cloud validator `fields` to be key value pairs
Open
Nobody has claimed this yet.
type:feature
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
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
The cloud validator option fields accepts either an array of strings which have no implict types, or an object that has .type.
Feature / Enhancement Description
Add option for fields to be an object, with key value pairs, where the key is the field, and the value is the type. Such as:
fields: {
data: Array,
},
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 locating the cloud validator implementation and its existing tests for the fields option. Add coverage for key-value field definitions such as data: Array while preserving the current array and .type forms; done means the new form is accepted with the expected type behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100