-
Notifications
You must be signed in to change notification settings - Fork 36
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
BUG 🐛: <Footer>
gets rewritten to <footer>
+ all other case insensitive html tag collisions
#4
Comments
Yup there's already a test for this at
but thanks for pointing it out! I still need to look into the parser to see why this is happening D: |
<Footer>
gets rewritten to <footer>
+ all other case insensitive html tag collisions
<Footer>
gets rewritten to <footer>
+ all other case insensitive html tag collisions<Footer>
gets rewritten to <footer>
+ all other case insensitive html tag collisions
<Footer>
gets rewritten to <footer>
+ all other case insensitive html tag collisions<Footer>
gets rewritten to <footer>
+ all other case insensitive html tag collisions
I'm working on this issue now. Inline components without '{' are considered not to be jsx.
and run
another problemI used VScode and executed the above command in the terminal. It worked as expected.
Does anyone else have the same problem? reproduction1 |
When an imported component has a tag reference name that collides with one of the standard tag names in HTML - like for instance <Footer /> - the plugin resets it to <footer />. Thus being lowercase then it won't get rendered by astro and the component is missing in the output.
I don't like the clunkiness of having to keep a complete nomenclature in mind to avoid collisions like these.
Also the compiler doesn't complain - how could it be aware? - so the then missing component gets dropped silently.
The text was updated successfully, but these errors were encountered: