-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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: improve invalid nested interactive element error #10199
Conversation
🦋 Changeset detectedLatest commit: ea03870 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 |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -530,6 +531,19 @@ export const validation = { | |||
} | |||
} | |||
|
|||
if (interactive_elements.has(node.name)) { |
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.
Should this use the more complete disallowed_contents
from the util instead?
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.
I initially tried that., but it gets complicated, as you can nest some contents there (if you nest a table inside a cell of another table, this is valid).
I thought we were doing this already somewhere? This ensures we correctly check for invalid nested interactive elements.