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

Introduce a mechanism to enable and disable plugins explicitly #422

Open
8 tasks
obfischer opened this issue Mar 22, 2020 · 0 comments
Open
8 tasks

Introduce a mechanism to enable and disable plugins explicitly #422

obfischer opened this issue Mar 22, 2020 · 0 comments
Assignees

Comments

@obfischer
Copy link
Contributor

Userstory

As a user of jQA,
I would like to have a mechanism to enable and disable plugins of jQA explicitly,
so that I have a better control of the plugins jQA runs during a invocation.

Rationale

jQA offers a wide range of plugins for scanning, running concepts and constraints and for various reports.
Currently we run all of them during a single invocation of jQA. Each plugin we run prolongs the execution time and the might increase the size of the used Neo4j database, even if the result of a plugin is not needed by the user.
Allowing the user to enable of disable plugins gives him more control over these aspects and can result in a faster scan or a smaller database. The advantage of a smaller database is also that it might become easier to query the database as it might contain fewer labels or nodes.

Acceptance Criteria

  • Each core plugin has a unique id and for the user easy to remember identifier
  • Each plugin can by explicitly disabled
  • Each plugin can by explicitly activated
  • Having an id is optional for a plugin to avoid problems with third party plugins should issue a warning
  • If jQA finds an plugin without an id jQA
  • Without any given configuration jQA will run all plugins
  • It is possible to disable all plugins and to enabler some plugins afterwards explicitly
  • The meachnism is well documented
@yaseno2186 yaseno2186 transferred this issue from jqassistant-archive/jqa-core-framework Jul 10, 2024
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

2 participants