As a first PR, let's add ethlint as a dependency. Having a consistent code style doesn't add any additional work in the long run, and reduces friction when reviewing code.
I use yarn usually, after running that to build the packages you can run yarn lint to see the output.
The linting rules are set in .soliumrc, and we can change them if we find them inappropriate (usually the discussion is about the max length allowed in each line).
In my projects I usually set a clean lint run as a condition for merging branches. Not going to propose that here yet, but as the project grows it will be necessary.
As a first PR, let's add
ethlintas a dependency. Having a consistent code style doesn't add any additional work in the long run, and reduces friction when reviewing code.I use
yarnusually, after running that to build the packages you can runyarn lintto see the output.The linting rules are set in
.soliumrc, and we can change them if we find them inappropriate (usually the discussion is about the max length allowed in each line).In my projects I usually set a clean lint run as a condition for merging branches. Not going to propose that here yet, but as the project grows it will be necessary.