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

Use static analysis/code quality service #109

Open
fdiblen opened this issue May 27, 2021 · 2 comments
Open

Use static analysis/code quality service #109

fdiblen opened this issue May 27, 2021 · 2 comments

Comments

@fdiblen
Copy link

fdiblen commented May 27, 2021

Using a service like Codacy or Sonarcloud will give more insights about improvements you can make.

@egpbos
Copy link
Collaborator

egpbos commented May 27, 2021

Duplicate of #95

@egpbos egpbos marked this as a duplicate of #95 May 27, 2021
@egpbos egpbos closed this as completed May 27, 2021
@egpbos
Copy link
Collaborator

egpbos commented May 27, 2021

Actually, #95 was just about PyLint, but Codacy does a bit more. Most issues there are just from PyLint. However, it also does code duplication detection, which is kinda nice. Maybe we could use that later on to clean up the code a bit more.

It was very easy to activate, so I did, the results can be browsed here: https://app.codacy.com/gh/spokenlanguage/platalea/dashboard

It should be easy to add a badge to the README at some point, so I'll just leave this open to remind us.

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

No branches or pull requests

2 participants