Add @SuppressAssertingFormats annotation for fine-grained control over AssertingCodec formats
#15468
+54
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces a new
@SuppressAssertingFormatsannotation that allows test classes tosuppress specific asserting formats within the
AssertingCodecwhile keeping other assertingformats active.
Currently,
@SuppressCodecs("Asserting")disables the entireAssertingCodec, losing allassertion checks. However, some tests have legitimate use cases to just suppress specific
AssertingFormatsand continue withAssertingCodec.Now With this we can use as
@LuceneTestCase.SuppressAssertingFormats("AssertingStoredFieldsFormat")rather than@SuppressCodecs("Asserting")