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
{{ message }}
This repository was archived by the owner on May 14, 2021. It is now read-only.
Surely this isn't how importName should work. I would expect only tagged templates which use the specified import name to be parsed, rather than ALL imported names and the extra styled-specific stuff.
Like this:
// moduleName = module// importName = yimport{x,y}from'module';x`test`;// NOT parsedy`test`;// parsed
With this ability we could use the same component on other tagged template css libraries. Something like LitElement. But we can't yet because we over-parse:
css`this is css`;// parsedhtml`this is html`;// parsed <- WRONG, it shouldn't be
The text was updated successfully, but these errors were encountered:
Agree with your feature request. But importName is there. We have use another option name or try to enhance it. Like single string means the old usage, and an array is used to provide names whitelist.
So you provide two options:
moduleName
importName
Used like so:
Surely this isn't how
importName
should work. I would expect only tagged templates which use the specified import name to be parsed, rather than ALL imported names and the extra styled-specific stuff.Like this:
With this ability we could use the same component on other tagged template css libraries. Something like LitElement. But we can't yet because we over-parse:
The text was updated successfully, but these errors were encountered: