parse-community / parse-community/parse-server-example
Evolve Example package
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.9k
- Forks
- 5.3k
- PR merge metrics
- No merged PRs in 30d
Description
Some ideas for evolution of Parse Server example:
Have multiple branches, with different levels of complexity, such as:
- dev - the most simple Parse Server
- cjs - commonJS version of Parse Server
- prod - a Parse Server with some recommended user triggers, allowClientClassCreation, etc
- AWS Secrets - a Parse Server utilising a secret manager
- definedSchema - Parse Server with defined schemas (@sadortun your input would be welcomed here)
- typescript - Parse Server with Typescript
- react - Parse Server with a react frontend
- vue - Parse Server with a VueJS frontend
- dashboard - Parse Server with a Parse Dashboard
- graphQL - GraphQL Parse Server
- cluster - Parse Server with clustering
Contributor guide
No contributing guide indexed for this repository
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
The issue lists possible example variants, including cjs, prod, definedSchema, typescript, frontend, dashboard, graphQL, and cluster, but names no files, tests, or entry points. First clarify which variant is wanted and its scope; completion is not defined for the broader evolution request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- express, javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100