-
Notifications
You must be signed in to change notification settings - Fork 11
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
Deprecate/remove default tags. #52
Milestone
Comments
Will that impact react-next? If so, any idea what I should be doing to be compatible? |
Nope, react-next uses its own generator, which simply put knows what a |
back2dos
added a commit
to MVCoconut/coconut.vdom
that referenced
this issue
Jul 7, 2021
back2dos
added a commit
to MVCoconut/coconut.react-dom
that referenced
this issue
Jul 7, 2021
Well, after removing them and trying to migrate a bigger project I've realized this is a pita. Should deprecate instead. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Default tags are used to bring
<div />
and such into scope. They complicate tag resolution a lot (which in turns makes supporting IDE services all the harder) and they really just save the user one*
import (which can go intoimport.hx
).I'm inclined to remove them straight away, in favor of a clear error message - unfortunately, the user will get to see it in builds, but not in diagnostics, but I suppose most hxx (i.e. coconut) users are pretty used to IDE services being weird.
The text was updated successfully, but these errors were encountered: