Linter #936
rvcas
started this conversation in
Help welcomed
Linter
#936
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What is your idea? Provide a use case.
We would like to entertain the idea of a brand new subcommand on the aiken CLI:
Why is it a good idea?
Ideally this runs even more sophisticated analysis beyond what is done in
aiken check
.If this can be accomplished there are also quite a few warnings that can be moved from
aiken check
to the "linter".Inspirations:
What is the current alternative and why is it not good enough?
aiken check
works fine and provides quite a few warnings already BUT there's a bit of a limit to the number of checks that we could do before we start to hamper the performance of a command that is ran very often. Not only isaiken check
responsible for the typechecking but it also typechecks, compiles, and runs your tests. Due toaiken check
potentially carrying heavy workloads especially in large projects (depending on number of tests etc.) we think we need a companion tool normally known as a linter.Beta Was this translation helpful? Give feedback.
All reactions