parse-community / parse-community/parse-server
Add object-shorthand lint rule
Nobody has claimed this yet.
- 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
Without enforcement of stronger lint rules, there is no consistent styling across Parse Server.
Feature / Enhancement Description
Add object-shorthand lint rule so that there is consistency across function declarations.
ECMAScript 6 provides a concise form for defining object literal methods and properties. This syntax can make defining complex object literals much cleaner.
Example Use Case
n/a
Alternatives / Workarounds
n/a
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 with the ESLint object-shorthand rule documentation linked in the issue, then locate Parse Server's lint configuration and existing rule tests. Enable the rule for the project and verify that the lint checks pass with consistent object method and property shorthand usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100