[TwigComponent] Html syntax bug test case + fix #824
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
weaverryan
changed the title
|
Now this also has the fix :) |
weaverryan
force-pushed
the
twig-html-syntax-test-cases
branch
from
c609746 to
769b55a
Compare
weaverryan
force-pushed
the
twig-html-syntax-test-cases
branch
from
769b55a to
c3854cc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Not a fix, just a test case for the bug described in #805. It's probably easy to fix.
This fails to add the correct
contentblock inside oftwig:foo:But if you add any non-whitespace character before
<twig:bar>- e.g.foo <twig:bar>- then it WILL add the block correctly. So, just some small thing not looking for an embedded component as valid "content" that should open that content block.