-
Notifications
You must be signed in to change notification settings - Fork 66
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
Fix incorrect table parsing when it contains expressions in certain cases #925
Conversation
🦋 Changeset detectedLatest commit: 4d23d09 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
!preview table-tr-expr-issue |
|
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.
Amazing, thank you so much for tackling this!
Changes
Inside a
table
element, when there was an impliedtr
tag which had atd
orth
which contained an expression (that's a mouthful yeah 😅), it would cause any trailing element/component/text node to be swallowed by the table element (just before thetable
closing tag). This fixes that.Testing
Docs
N/A bug fix