Custom Tokens Light/Dark separation not possible?

[dHoangBach]

Hello, it seems like that it is not possible to have custom tokens that change depending on light or dark mode.
With the new update to PrimeOne 4.0.0 it would have make sense to create custom variables that are separated into the light and dark modes but sadly my theme designer only displays the values of the most right mode (dark).

Is there any way to go around this issue or is this just not a possibility? Could there be an update in the future?

[cloddo]

Hello, I'm facing the same issue. In Figma, when adding a custom token, both a light and dark value are requested. However, the exported theme fails to generate a light and dark colorScheme, exporting only the dark mode values instead. This appears to be a bug, and a prompt fix would be greatly appreciated given that these are paid features.

[cagataycivici]

I believe you can juse use light-dark when defining your custom token. In PrimeUIX themes, we're deprecating colorScheme object in favor of CSS native light-dark, much simpler. The generated code and the default presets already use light-dark. Custom tokens can support it as well.

[cagataycivici]

Please send your tokens.json to contact at primetek.com.tr so the team can review your custom tokens. We can continue discussion here. PrimeTek will announce a huge launch of the new products in June so whole team is extremely busy but we'll try to have a look for sure to see if we can do a quick improvement.

[cloddo]

Thank you for looking into this, I have just emailed our tokens.json to the support address you provided.

[cagataycivici]

Thanks, we've reviewed and I think it requires changes on the PrimeUI Theme Generator plugin. We're few weeks away from the big launch so added to our backlog for now until the launch. We should be able to handle it at the plugin side without waiting for the new UI Kit which will take more time.

[cloddo]

Thank you for the update. While I understand that the upcoming launch is your main priority, a 'few weeks' plus the time to process the backlog after the launch may unfortunately be too late for us.

We are in the middle of an active development phase right now. By the time the plugin is updated, we may be past the point where we need to generate these exports, meaning we would have to look for alternatives or absorb the manual overhead... this is quite disappointing for a paid product.

[cagataycivici]

I'm afraid, that's the best thing we can do at the moment. There are countless of enhancements planned in the pipeline which takes time to prioritize and implement.