Skip to content
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

Merged
merged 3 commits into from
Jan 16, 2024

Conversation

trueadm
Copy link
Contributor

@trueadm trueadm commented Jan 16, 2024

I thought we were doing this already somewhere? This ensures we correctly check for invalid nested interactive elements.

Copy link

changeset-bot bot commented Jan 16, 2024

🦋 Changeset detected

Latest commit: ea03870

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
svelte Patch

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

Copy link

vercel bot commented Jan 16, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
svelte-5-preview ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 16, 2024 1:45pm

@@ -530,6 +531,19 @@ export const validation = {
}
}

if (interactive_elements.has(node.name)) {
Copy link
Member

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?

Copy link
Contributor Author

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants