Since you don't have a package.json in your project, just know you should install it via npm install elm-review (globally if that's what you prefer), and then run npx elm-review or just elm-review depending on your system.
I have not fixed any of the errors, and there are quite a lot of them.
I recommend that you start by commenting every rule and turn them on one by one after you fix all the errors, starting with NoUnused.Variables for instance. Also, if you don't agree with the rule or don't the value, just remove it.
Some rules (like this last one) can be autofixed. So I recommend
running elm-review --fix, which will prompt you with every fix
or running elm-review --fix-all which will apply all the changes and you can then accept or refuse. Not recommended because fixes are not always perfect, but it can be useful to see the extent of changes you'll have to go through.
mdgriffith
commented
4 years ago
This adds an
elm-reviewto the project.Since you don't have a
package.jsonin your project, just know you should install it vianpm install elm-review(globally if that's what you prefer), and then runnpx elm-reviewor justelm-reviewdepending on your system.I have not fixed any of the errors, and there are quite a lot of them. I recommend that you start by commenting every rule and turn them on one by one after you fix all the errors, starting with
NoUnused.Variablesfor instance. Also, if you don't agree with the rule or don't the value, just remove it.Some rules (like this last one) can be autofixed. So I recommend
elm-review --fix, which will prompt you with every fixelm-review --fix-allwhich will apply all the changes and you can then accept or refuse. Not recommended because fixes are not always perfect, but it can be useful to see the extent of changes you'll have to go through.