Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a linter #24

Open
ftomassetti opened this issue Sep 8, 2019 · 3 comments
Open

Add a linter #24

ftomassetti opened this issue Sep 8, 2019 · 3 comments

Comments

@ftomassetti
Copy link
Member

In this way we do not have to review for styles issues

@sschuberth
Copy link

Probably Detekt with KtLint-based formatting rules enabled?

@sschuberth
Copy link

sschuberth commented Jan 25, 2024

I just found this discussion, but just as a remark, of course KtLint is way more Kotlin-specific style checks than .editorconfig, and via Detekt it's also not "a PITA" to configure anymore.

@lppedd
Copy link
Contributor

lppedd commented Jan 25, 2024

My point for preferring Editorconfig over tools like KTLint (and Detekt) is simplicity, both for the IDE and for build scripts.
With Detekt we're adding layers of additional complexities for simple formatting issues, which we solve nicely with the auto-recognized .editorconfig file.

Tools like Detekt are generally useful for big teams or a large number of contributors, but in this case we're not at that point and a simple CTRL+ALT+L (on Windows) fixes everything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants