[Validator] BicValidator - fixed raising violations to a maximum of one #16806
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
|
@mvhirsch to test this add your test case to the list in the |
|
Thank you @mvhirsch. |
fabpot
added a commit
that referenced
this pull request
Dec 18, 2015
…aximum of one (mvhirsch) This PR was merged into the 2.8 branch. Discussion ---------- [Validator] BicValidator - fixed raising violations to a maximum of one | Q | A | ------------- | --- | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | none | License | MIT | Doc PR | none I just found a bug while using the constraint. For example my value "a" will raise three violations at one time. I just expected to get a maximum number of one. This PR will fix that behavior. I do not know how I can easily add Unit-Tests for that, can someone please help me? Commits ------- 7860bb4 [Validator] fixed raising violations to a maximum of one
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I just found a bug while using the constraint. For example my value "a" will raise three violations at one time. I just expected to get a maximum number of one.
This PR will fix that behavior.
I do not know how I can easily add Unit-Tests for that, can someone please help me?