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

Ability to configure issues at or after run time? #51

Closed
isclayton opened this issue Sep 9, 2022 · 2 comments
Closed

Ability to configure issues at or after run time? #51

isclayton opened this issue Sep 9, 2022 · 2 comments

Comments

@isclayton
Copy link
Contributor

I am testing this against a code base comprising >7k files (Java and JS mainly). The ensemble approach is great, but I have not been able to determine if it is possible to exclude issues from analysis and thereby speed up the overall analysis time.

The UI seems to have this functionality, but 1) the filtering API/current database schema does not seem to support selection or exclusion of e.g., "readbility" issues en masse (see my PR for a bug in this feature btw), and 2) manually deselecting via the on/off switch does not appear to affect scans currently in progress.

Any advise on how I can exclude issues from consideration for a scan, either before or after scan is started?

@marcinguy
Copy link
Owner

Hi @isclayton

Thank you for the issue and your PR contribution. Well, you will get a massive speed up with PRO (Professional) paid version (up to 4x+ times).

If you would like to contribute with code or financially (GitHub sponsor, PRO license) please let me know via DM. Always look for folks to join the project.

I can explain you async/off GH issues more.

Betterscan is an effort to create and maintain and with PRO version we offer certified speed up with scanning and it enables commercial support for the project.

Hope you understand.

Thanks,

@marcinguy
Copy link
Owner

Closing due to inactivity

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
@isclayton @marcinguy and others