parse-community / parse-community/parse-server
Add lint rule to require new line at end of file
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
Currently, lint rules not require an empty new line at the end of a file.
-
This requirement should be consistent across repos, we currently require it in the the Parse Android SDK.
-
There is a good argument for adding the rule:
Trailing newlines in non-empty files are a common UNIX idiom. Benefits of trailing newlines include the ability to concatenate or append to files as well as output files to the terminal without interfering with shell prompts.
Feature / Enhancement Description
Add lint rule eol-last.
Example Use Case
n/a
Alternatives / Workarounds
n/a
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 checking how existing lint rules are defined. Enable the requested eol-last rule, then run the lint checks; done means files are required to end with a newline and the lint run passes.
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
- 50/100