We were inspired by two things
- A novel domain. All of the team has experience in full stack web development, but we had no experience in building dev tools or knowledge of how compilers/interpreters/devtools interpret code.
- PR Review Process: generally in PR review, people point out the flaws in your code we wanted to make something that does the opposite, it commends you for doing a good job. ## What it does
It can be used in two ways
- as a cli
- as a node module. in which case, it would return all of the good changes made as an array of object where each object contains a message and a line number on which to display that message. this was a big goal for us since this enables integration with software such as VSCODE or github actions.
How we built it
Challenges we ran into
- having no familiarity with how code is processed.
- one member of the team had very less familiarity with JS.
Accomplishments that we're proud of
The fact that we pulled this off, something that we didn't know anything about a week ago, and we learned a lot in the process.
What we learned
- how code is processed
- how packages are published to npm
- how github actions can be used for CI
What's next for nice-linter
- integrate it with github actions and vscode
- make the process of adding more rules simple, sort of a custom syntax or a DSL if you will. Currently, adding new rules is only possible through actual coding, like eslint plugins. but we want to experiment with making it more easy.