parse-community / parse-community/parse-server
Allow `Schema.definitions` to be a file
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
I like to store a JSON file with the SCHEMA definition. It could be nice to be able to set definitions via:
schema: {
definitions: 'schema.json'
},
Feature / Enhancement Description
Allow setting a file to schema definitions
Example Use Case
schema: {
definitions: 'schema.json'
},
Alternatives / Workarounds
const definitions = await fs
.readFile('spec/support/schema.json', 'utf8')
.then(file => JSON.parse(file));
schema: {
definitions
},
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 how the schema configuration and its definitions entry are read, using the issue's schema.definitions example as the expected input. Check the existing schema-related tests or configuration entry points, then verify that a definitions path such as schema.json is loaded and parsed with the same behavior as inline definitions.
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
- 35/100