-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EZP-29301: Added support for custom attributes on elements #35
EZP-29301: Added support for custom attributes on elements #35
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add some test fixtures for this feature to https://github.com/ezsystems/ezplatform-richtext/tree/master/tests/lib/eZ/RichText/Converter/Xslt/_fixtures
Otherwise we have no way of tracing regressions when doing changes. It also gives better overview of what the feature provides.
@alongosz will do it a bit later today |
ping @alongosz for another review :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only concern I have here is naming which is not consistent with other existing names.
We've decided with @dew326 that we want:
- for DocBook:
ezattribute
- for OE XHTML5 format:
data-ezattribute-...
.
Additionally I'd change Relax NG definition name to ez.xhtml.data.attribute
looking over existing naming convention. This one has no impact on processed DocBook or output for OE.
Below there are some examples of needed changes, but it needs to be fixed in more places:
src/lib/eZ/RichText/Resources/stylesheets/docbook/xhtml5/output/core.xsl
Outdated
Show resolved
Hide resolved
src/lib/eZ/RichText/Resources/stylesheets/docbook/xhtml5/output/core.xsl
Outdated
Show resolved
Hide resolved
…tom-attribute-<attr>
@alongosz done. Please review. |
Allows storing custom attributes. This PR does not provide any UI to modify/edit them in Online Editor. But it lets you migrate content from eZ Legacy to eZ Platform.
We used the following example content for tests:
Generated content in Online Editor:
Output:
TODO:
$ composer fix-cs
).// Maintainer edit: updated PR title and issue type - this is not a bug, it just was not supported yet in the new stack