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

Evaluate the approach underlying Graal #89

Open
valeriocos opened this issue Feb 12, 2020 · 0 comments
Open

Evaluate the approach underlying Graal #89

valeriocos opened this issue Feb 12, 2020 · 0 comments

Comments

@valeriocos
Copy link
Member

Graal contains 6 backends that allow to fetch different kind of information from source code (complexity, licenses, dependencies, etc.). Each backend can fetch source code information using different tools. For instance, coqua relies on pylint and flake8 for code quality, colic leverages on nomos and scancode to get license insights. Every time a backend is enhanced to support a new tool, the corresponding code looses cohesion and the maintenance/evolution effort increase.

The goal of this ticket is to evaluate a different approach for graal backends, where each backend relies on a single tool. In this case scenario, there will be a backend for flake8, pylint, nomos and scancode.

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

1 participant