Linting / Precommit Hooks
Could use some standardization and some dev environment hook setups to keep the code structure clean
@TrevorBurgoyne @csolbs24
I'm thinking we go with ESLint and prettier, with both being ran as pre-commit hooks.
Any qualms with these? If there's something we'd rather use, I'm open to it.
I'll have a PR with the formatting changes so that we can split hairs over linting/formatting rules before anything is official.
I opened #175 as a draft. It uses husky as I liked it's terminal outputs better than the pre-commit on npm (which is apparently different from the python one).
ESLint finds 232 errors so it might be wise to merge it and fix files as they're edited. Thoughts?
#175 solves some initial linting/formatting concerns.
Three things we haven't addressed:
- [ ] JSDoc / TSDoc enforcement
- [ ] Line length
- [ ] Importing sorting / automatic removal of unused imports