A placeholder issue to propose a consistent and clearer wording of Component validator wording messages
Issue fork ui_patterns-3462737
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
pdureau commentedComment #3
pdureau commentedI have started a table to follow the changes (still empty, but let's work on it the next days): https://docs.google.com/spreadsheets/d/1uLGS_knoJ5dQ96lh2pmEUnthzok28K1l...
Comment #4
pdureau commentedAlso, add an annotation in the messages which are addressed to component authors targeting UI Patterns instead of low-level SDC. For example, "You should declare a story in the definition"
Comment #5
kristen polAnd perhaps whether it's a Twig thing vs SDC thing, e.g.
starshot_demo:button Error The exact same as just testing the Twig 75 {% if attributes is not empty %}{{- attributes|raw -}}{% endif %}
Comment #6
kristen polNot to do with wording but it would be nice to be able to just get Schema warnings/errors or just Twig and to be able to "turn off" some things (e.g. Notices).
Also, should the "Unknown variable: is_dismissable" in the Twig maybe show up as a notice in the schema list? Not sure but perhaps easier if people are focused on fixing the schema vs the twig.
Comment #7
pdureau commentedThanks for your feedbacks. We will work on this in second half of August.
Comment #8
kristen polAwesome 👏
Comment #9
pdureau commentedBeta2 is coming soon and we are late, so let's do only this for beta2:
From error to warning, related to components embedding:
From error to warning, related to Twig condition testing:
Other stuff:
I will move everything else, including the wording, to beta3
Comment #12
mogtofu33 commentedDone changes requested in #3462737-9: [2.0.0-beta2] Component validator: move some errors to warnings
Comment #14
pdureau commentedGreat. Merged.
Follow-up #3473578: Component validator wording & rules
Comment #15
pdureau commented