Jakob Engelbrecht

@mathieubergeron @reintroducing @vincentbriglia I can confirm that removing `jsesc` from the mix now creates nicely formatted release messages in Teams (we create a copy of the plugin wihin our repo...

@fredboyle for the `css/variables` format and your custom formats this can be achieved by using the `outputReferenceFallbacks` option: https://amzn.github.io/style-dictionary/#/formats?id=custom-format-helpers

Hey @mihkeleidast , thx for sharing your solution 👍🏻 I agree with @six7 that this should be tackled at the transformation level, instead of expanding the shadow token. There will...

> This would be a bit more difficult, but nothing is impossible. The difficulty in this approach is the end result for the generated code for each platform would mean...

Hey, we've experienced the same issue, so I'll just chime in with our findings / solution: When outputting typography css classes, it's really useful to have all the properties for...

Hey, I can chip in here, as we're doing something similar to @lennartbuit. In our approach we are rendering individual css files for each component in a component library and...

> Also in #688 @chazzmoney I see this is related, but to me that's a more general issue about supressing warnings where as this issue is specifically about outputting references.

Hi @six7 , I've cleaned up the code and moved all new functions to separate files as suggested - as well as removed some code duplication. I've tried to follow...

> Hey @jakobe - we finally merged the theme / style id connections changes into `next`. Do you mind merging `next` into your branch and giving it a go if...

> Hey @jakobe - we finally merged the theme / style id connections changes into `next`. Do you mind merging `next` into your branch and giving it a go if...