fix(DBOjbect): Display attribute value in uniqueness rule message#855
Open
Hipska wants to merge 1 commit intoCombodo:developfrom
Open
fix(DBOjbect): Display attribute value in uniqueness rule message#855Hipska wants to merge 1 commit intoCombodo:developfrom
Hipska wants to merge 1 commit intoCombodo:developfrom
Conversation
Contributor
Author
|
IMHO, this rule should have been named |
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
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.
Base information
Symptom
The generic uniqueness rule message for
no_duplicatedisplays the field label twice:Reproduction procedure
uniqueness_rules/rulewith idno_duplicatein the class datamodel.Cause
The
DBObject::GetUniquenessRuleGenericMessagemethod wrongly callsAttributeDefinition::GetLabelwith the attribute value as parameter.Proposed solution
Call
AttributeDefinition::GetValueLabelinstead.I could not add a test for this case in
UniquenessMessageTest, since (I think) there are no uniqueness rules without a custom message and without externalkey attributes in the standard datamodel.Checklist before requesting a review