-
-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reference tokens not correct #293
Comments
I'm seeing this as well |
Yes, it would be really nice if that could be fixed. |
Any updates here? |
I can also reproduce this. This sadly makes the plugin unusable :/ |
Sorry I missed this. I will loom into the Pr by @JackHowa to merge it |
Hey, I looked into it but it is not as easy as you made it seem. 🤣 @JackHowa can you please just add the needed test to the PR you made? #289 Only the test please. Happy to look into the other PR you closed as a separate one. But I would love the PR to stay as it is and just add a test so I don't have to re-review and can merge it as soon as the test is there. 🙏 |
ah I didn't make that pr linked #289 but I can see if I can make a clean pr for ya |
here's the updated pr #300. I had to break out some utils so they were easier to test |
Okay, I merged and released this now. Can you please test if this fixes it? |
Yep works for me! |
Hi,
When I generate json tokens, the references are incorrect.
Example :
I have 3 modes "Theme A", "Theme B", "Theme C".
Each value reference take the last mode (theme C)
"value": "{colors.themeC.palette.brand.secondary}"
Reference value must be {colors.themeA.palette.brand.secondary}
The text was updated successfully, but these errors were encountered: