- Issue created by @ckng
- Merge request !111Issue #3482516 by ckng: Inconsistent `attributes` handling → (Merged) created by ckng
- 🇲🇾Malaysia ckng
These are initial fixes. Note that haven't gone through all the components yet.
Unsure items, not used or will break backward compatibility, ie. subtheme needs to be updated:- comment
- field
- field-comment
- fieldset
- nav
- node
- 🇲🇾Malaysia ckng
Backward incompatible tracking for subtheme:
- templates/field/image.html.twig - 🇫🇷France pdureau Paris
Standardize all components implementation, use a unique `COMPONENT_attributes`, which can be passed `attributes` as needed.
If you do that, you will have both
COMPONENT_attributes
andattributes
in your template.It seems you have another problem to fix, probably in the way your are calling the components.
For example, instead of doing that:
{% include 'radix:image' with { image_attributes: attributes, responsive: true, }
You may need to use the
only
keyword:{% include 'radix:image' with { attributes: attributes, responsive: true, } only
- First commit to issue fork.
Thanks a lot ckng, merged.
Pierre I'll check and see what we can do.Automatically closed - issue fixed for 2 weeks with no activity.