Replies: 2 comments
-
regarding type-safety with TS, this is not really possible, see #1776 (reply in thread) we will add warnings logs for these |
Beta Was this translation helpful? Give feedback.
0 replies
-
Understandable, thanks! A warning would be helpful. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Description
When I create a semantic token which references another token, I expect to have some kind of checking to prevent me from referencing tokens which don't exist when I have
strictTokens: true
,In this example I can reference
mySemanticTokenTypo
in my code and I won't get any type errors (that makes sense, it's a valid token!) but the underlying CSS references a variable which doesn't exist:and I get no warning about this anywhere.
Link to Reproduction
https://play.panda-css.com/gfgL5aFu42
Steps to reproduce
No response
JS Framework
React (TS)
Panda CSS Version
0.27.3
Browser
No response
Operating System
Additional Information
I don't mind where I get an error, I would just like one somewhere so I know I've made a mistake.
At a minimum I think it would make sense for the compiler to report an error if it encounters the
{}
syntax inside a token which references something that doesn't exist.Beta Was this translation helpful? Give feedback.
All reactions