- Issue created by @bernardopaulino
- 🇧🇪Belgium bernardopaulino Brussels
bernardopaulino → changed the visibility of the branch 3541367-improve-validreferenceconstraint-error to hidden.
- 🇧🇪Belgium bernardopaulino Brussels
bernardopaulino → changed the visibility of the branch 3541367-improve-validreferenceconstraint-error to hidden.
- 🇧🇪Belgium bernardopaulino Brussels
bernardopaulino → changed the visibility of the branch 3541367-improve-validreferenceconstraint-error to active.
- Merge request !12994Improve ValidReferenceConstraint error messages by including bundle information → (Open) created by bernardopaulino
- 🇧🇪Belgium bernardopaulino Brussels
I created a new Merge Request which implements the improvements proposed in the issue description.
- 🇧🇪Belgium borisson_ Mechelen, 🇧🇪
I think this might work for some entity types, but not for all, one of the errors I see in the tests is this one:
user_id.0.target_id=This·entity·(user·-·User:·2)·cannot·be·referenced.||flvpwaxl.0.format=The·value·you·selected·is·not·a·valid·choice.'
This reference (user - User: 2) doesn't seem to add any value and I think only adds confusion. At the very least this needs to be fixed so that users don't have the double reference.
For paragraphs, I see value in this.