You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A type definition should be generated for .selector-1.
Actual behavior:
Currently .selector-1 is ignored and no type definition is generated.
Suggestion
This would be a breaking change, but would solve this issue without having to convert the names to something else (and potentially causing conflicts).
Instead of the current definition files that are generated:
exportconstselecter2: string;
You generate a class with static members. These can be defined with quotes around them, allowing for kebab case.
Enhancement
Package Version: 4.0.0
Code
widget.m.css
widget.m.css.d.ts
Expected behavior:
A type definition should be generated for
.selector-1
.Actual behavior:
Currently
.selector-1
is ignored and no type definition is generated.Suggestion
This would be a breaking change, but would solve this issue without having to convert the names to something else (and potentially causing conflicts).
Instead of the current definition files that are generated:
You generate a class with static members. These can be defined with quotes around them, allowing for kebab case.
Imports for the CSS would be where the breaking change occurs. You would need to change the import from:
to:
But the type check will still work.
Valid
Valid
Property 'selector-n' does not exist on type 'typeof css'.
The text was updated successfully, but these errors were encountered: