-
Notifications
You must be signed in to change notification settings - Fork 288
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
[suggestion] Allow the mechanism for creating a file name for frozen violations to be specified via an SPI or similar. #1045
Comments
danhaywood
changed the title
[suggestion] Allow the
[suggestion] Allow the mechanism for creating a file name for frozen violations to be specified via an SPI or similar.
Jan 20, 2023
On closer inspection, I see that the code in question is in |
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Jan 20, 2023
…hanism can be more easily overridden
I've raised a PR #1046 for your consideration. |
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Jan 22, 2023
…hanism can be more easily overridden Signed-off-by: Dan Haywood <dan@haywood-associates.co.uk>
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Jan 22, 2023
Signed-off-by: Dan Haywood <dan@haywood-associates.co.uk>
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Jan 22, 2023
so that it can be subclassed from any package Signed-off-by: Dan Haywood <dan@haywood-associates.co.uk>
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Jan 22, 2023
…hanism can be more easily overridden Signed-off-by: danhaywood <dan@haywood-associates.co.uk>
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Jan 22, 2023
Signed-off-by: danhaywood <dan@haywood-associates.co.uk>
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Jan 22, 2023
so that it can be subclassed from any package Signed-off-by: danhaywood <dan@haywood-associates.co.uk>
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Jan 22, 2023
(for inheritance) Signed-off-by: danhaywood <dan@haywood-associates.co.uk>
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Jan 23, 2023
Signed-off-by: danhaywood <dan@haywood-associates.co.uk>
In the meantime, I've copied out the
with
|
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Jan 25, 2023
…y defined extension point of TextFileBasedViolationStore Also marked public methods as final to limit the inheritance contract
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Jan 25, 2023
…y defined extension point of TextFileBasedViolationStore Also marked public methods as final to limit the inheritance contract Signed-off-by: danhaywood <dan@haywood-associates.co.uk>
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Feb 5, 2023
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Feb 5, 2023
Signed-off-by: danhaywood <dan@haywood-associates.co.uk>
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Feb 5, 2023
so that it can be subclassed from any package Signed-off-by: danhaywood <dan@haywood-associates.co.uk>
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Feb 5, 2023
(for inheritance) Signed-off-by: danhaywood <dan@haywood-associates.co.uk>
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Feb 5, 2023
Signed-off-by: danhaywood <dan@haywood-associates.co.uk>
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Feb 5, 2023
…y defined extension point of TextFileBasedViolationStore Also marked public methods as final to limit the inheritance contract Signed-off-by: danhaywood <dan@haywood-associates.co.uk>
danhaywood
added a commit
to danhaywood/ArchUnit
that referenced
this issue
Feb 5, 2023
Signed-off-by: danhaywood <dan@haywood-associates.co.uk>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
this follows on (somewhat) #1025.
We have a modular monolith, and have set up archunit to run for each module. We are using frozen violations to manage the technical debt in each module, to prevent new violations from being added and to chip away at old ones.
In some circumstances Archunit will recreate the guid files with the current set of violations, which in theory is a good thing but we find that the guid file can sometimes change. Perhaps our workflow is wrong, but at any rate, when multiple developers on current feature branches, we find we get a bunch of git conflicts that need to be resolved.
What we think would work for us is if the file name storing the violations for a rule were deterministic rather than a guid. Looking at the code, this is done at https://github.com/TNG/ArchUnit/blob/main/archunit/src/main/java/com/tngtech/archunit/library/freeze/ViolationStoreFactory.java#L166 , so the suggestion is to provide an SPI that makes this strategy pluggable.
The text was updated successfully, but these errors were encountered: