Skip to content
This repository has been archived by the owner on Jan 16, 2024. It is now read-only.

Nested JSX broken #35

Open
ElitoGame opened this issue Nov 13, 2023 · 2 comments
Open

Nested JSX broken #35

ElitoGame opened this issue Nov 13, 2023 · 2 comments

Comments

@ElitoGame
Copy link

Hey! I tried using nested JSX today, but couldn't get it to work in my Astro/Solid Project. While I didn't think my setup would break it (cause I actually got them running together, using 2 i18next libraries, but the same translation files), I decided to test them in a sample project, as illustrated in the following picture:

Screenshot, showing package.json, solid source code & html/console output

I have followed the instructions of the README.md, and installed html-parse-string, as well as done the general setup of a standard translation project. However, the console is still shouting errors, telling me to install html-parse-string. Since taking that screenshot, to make sure my results are not version dependent, I have upgraded my all package versions of my package.json, from default solid ts template, to be on par with solid-i18next, but the result is identical.

If you need further infos, etc, feel free to let me know, I'm happy to help =)

(Also let me know if you need the source code of the example project, I can easily upload it to GitHub)

@ElitoGame
Copy link
Author

Oh and the example for nested JSX, might have an error, if I am not mistaken. Shouldn't all 3 placeholders be called name, not (name, name and fullName)?

@ElitoGame
Copy link
Author

Curiously, this does work however:
image
I guess cause this is just a regular string and not a JSX expression? Well, would still be cool to have both :)

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

No branches or pull requests

1 participant