parse-community / parse-community/parse-server
Add additional lint rules
Open
Nobody has claimed this yet.
type:ci
- Dominant language
- JavaScript
- Stars
- 21.4k
- Forks
- 4.8k
- Avg merge
- 7h 45m
- Merged PRs (30d)
- 11
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest version of Parse Server.
Issue Description
Linter currently allows empty blocks, particularly empty catch blocks. I come across these sometimes in code reviews. They are usually an indication of bad code quality and a likely cause for unnoticed bugs because they swallow any error.
I suggest to add no-empty to the linter and specifically disallow empty catch blocks.
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 repository's ESLint configuration and read the linked no-empty rule documentation, especially its option for empty catch blocks. Done means the lint configuration rejects empty blocks and empty catch blocks, with the existing lint checks still passing.
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
- 35/100