Typewind generates unescaped * className causing ts language server parsing errors
sigmachirality opened this issue · 2 comments
Figured out why I was having this issue: #24 - while some DaisyUI classes were properly typed, others weren't, and the ones that were and weren't were arbitrary.
Turns out in the generated file, it produced the following Property
As a result, all classes generated on lines after this one (such as hero-content) are broken. If this Property is escaped as follows:
The exported tw object typechecks with all members correctly. If you could look into pushing a hotfix to a.) escape this class as shown b.) remove the class c.) investigate whether this class is getting generated correctly (maybe it's supposed to be something else?) that would be great! I'm looking to use this library in production more but missing most of the classes from the tw object/having to monkey patch the export is far from ideal.
@sigmachirality Is this happening in the latest version. We have actually fixed this issue before as well in #9, but I'll take a look again: 56429a6
I bumped my version and it fixed it! My bad.