Actually use the linter lol

[slifty]

We have this super great linter all set up on the project, and what do I do? Nothing. I do nothing with it.

At this point most of the files have linting errors, and cleaning the project warrants an issue in itself.

In addition to fixing the linting issues, we should consider baking in a hook that requires linting to pass before a commit can register.

[reefdog]

I have found that satisfying the linter at the stub level of the project is annoying and can lead to premature work. (Like, rewriting a stateless component as a pure function to satisfy the linter when you know it'll use state soon.) But that's probably a minor and early-stage annoyance; satisfying the linter becomes increasingly valuable as the project ages.

[reefdog]

Also on this set of projects I've embraced VS Code for the first time, and while I still often feel like I'm typing with mittens compared to a proper text editor, the integrated linter has been spectacular for catching this stuff in real time. It never even occurred to me you might have to lint manually.

[slifty]

I use sublime and just haven't spent the 30 minutes to research and set up an IDE linter. I should do that.