Ensure <eztemplate> elements contains <ezcontent> child #113
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.
This change is to ensure conversion script creates customtags in the same way as admin-ui ( even though the previous behaviour also was also valid schema wise). admin-ui always creates a
<ezcontent/>
element beloweztemplate
, even though the custom tags has no content..eZ Platform version 2.5.6 and earlier will give fatal error on the following twig code for
<eztemplate>
elements which has no<ezcontent/>
sub element:See ezsystems/ezplatform-richtext#84 for more info.
TODO:
$ composer test
)$ composer fix-cs
).