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.

Sign up for GitHub

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

Jump to bottom

Allow adjusting file names of TextFileBasedViolationStore #1046

Merged
merged 2 commits into from
Feb 6, 2023
Merged

Allow adjusting file names of TextFileBasedViolationStore #1046

merged 2 commits into from
Feb 6, 2023

Commits on Feb 6, 2023

  1. make TextFileBasedViolationStore public API 

    At the moment it is quite impossible to make any adjustments to the default `TextFileBasedViolationStore`, since the class is fully hidden from the public API and can thus not be instantiated or modified with respect to the implementation (e.g. adjusting the file names of the store).
We now make it public API and allow users access to it, so it can be extended through delegation.

Signed-off-by: danhaywood <dan@haywood-associates.co.uk>
Signed-off-by: Peter Gafert <peter.gafert@tngtech.com>
    @codecholeric
    codecholeric committed Feb 6, 2023
    Configuration menu
    Copy the full SHA
    c58158c View commit details
    Browse the repository at this point in the history

  2. allow adjusting file names of TextFileBasedViolationStore 

    To make the rule violation files easier to read for humans, we now allow to customize the way the rule violation file names are created, based on the rule description.

Signed-off-by: danhaywood <dan@haywood-associates.co.uk>
Signed-off-by: Peter Gafert <peter.gafert@tngtech.com>
    @danhaywood @codecholeric
    danhaywood authored and codecholeric committed Feb 6, 2023
    Configuration menu
    Copy the full SHA
    d48e0e1 View commit details
    Browse the repository at this point in the history