test(validation): cover info-description marker spacer tolerance#354
Open
hdamker wants to merge 1 commit into
Open
test(validation): cover info-description marker spacer tolerance#354hdamker wants to merge 1 commit into
hdamker wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What type of PR is this?
tests
What this PR does / why we need it:
Adds regression coverage confirming that P-027 info.description drift checks tolerate blank presentation spacer lines adjacent to CAMARA mandatory block markers.
This covers the compatibility case raised from Commonalities#651 while Commonalities templates and API specs may not yet have matching delimiter-adjacent spacing.
Which issue(s) this PR fixes:
Related to camaraproject/Commonalities#651
Special notes for reviewers:
No checker implementation change is needed; the existing paragraph normalization already handles these delimiter-adjacent blank lines. This PR locks that behavior with explicit tests for API-only and canonical-only spacing around both BEGIN and END markers.
Changelog input
Additional documentation
This section can be blank.