You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently heard of a package called flint. Flint is similar to lintr, however, from the flint documentation, "lintr’s performance is not optimal when it is applied on medium to large packages. Also, lintr cannot perform automatic replacement of lints."
Lintr highlights lints but relies on the developer to fix them. Automating fixing some of the lints would be quite nice.
Implementation ideas
Either:
Create a new function, such as flint_r()
Update lint_r to include flint::fix() functionality to automatically address lints
I think option 2 makes more sense. Perhaps run flint::fix to fix lints and then run lintr to highlight which lints remain
Impact
Lintr is great but it doesn't automatically fix lints, flint does, which saves time. It's not the end of the world if flint isn't incorporated, but automation is great, and fixing lints by default vs opting in or fixing lints manually helps ensure greater code quality.
One thing to note is that there isn't 100% overlap between flint and lintr so developers would still have to manually fix lints not addressed by flint
Comments
Thanks for your consideration
The text was updated successfully, but these errors were encountered:
Motivation
Hi, all:
As always, thanks for the great work on Rhino.
I recently heard of a package called flint. Flint is similar to lintr, however, from the flint documentation, "lintr’s performance is not optimal when it is applied on medium to large packages. Also, lintr cannot perform automatic replacement of lints."
Feature request: Automatically fix lints
repo: https://github.com/etiennebacher/flint
Feature description
Lintr highlights lints but relies on the developer to fix them. Automating fixing some of the lints would be quite nice.
Implementation ideas
Either:
I think option 2 makes more sense. Perhaps run flint::fix to fix lints and then run lintr to highlight which lints remain
Impact
Lintr is great but it doesn't automatically fix lints, flint does, which saves time. It's not the end of the world if flint isn't incorporated, but automation is great, and fixing lints by default vs opting in or fixing lints manually helps ensure greater code quality.
One thing to note is that there isn't 100% overlap between flint and lintr so developers would still have to manually fix lints not addressed by flint
Comments
Thanks for your consideration
The text was updated successfully, but these errors were encountered: