Nahiyan Khan

@macintoshhelper Would love to check your additions! Do you have it public? 🙏

@macintoshhelper Understandable if thats the case! To @porada's point it seems like no permission is needed?

> @macintoshhelper @nahiyankhan > > Sorry for the long delay, I no longer work at Lyft, so I'm not sure who will take over the responsibility of this repo. This...

Do you have two name transforms then? The ordering of it would matter. Plus transitive: true. Alternate suggestion is to combine and have one custom name transform **or** a custom...

Style Dictionary relies on the "value" field to know when to process and transform a design token. The architecture section in the documentation is a good read about it. https://amzn.github.io/style-dictionary/#/architecture...

Glad it worked out! And thanks for the link - I wasn't aware of that. I just tried it and it appears to work in our implementation 😮 (we are...

@dbanksdesign has examples of colorsets and imagesets xcassets generation here: https://github.com/dbanksdesign/style-dictionary-dark-mode . It's what I have been relying on. They are set up as actions instead of formatters.

Hi there. I handled something similar in the past. The theory was, there is a global system and then local systems can extend the global system's tokens. We kept the...

In your custom transform, can you try with "transitive: true"? Reference: https://amzn.github.io/style-dictionary/#/transforms?id=transitive-transforms I just recently made a color adjustment transform too (for pressed / disabled / hovers) and scratched my...

Would something like the [multi-brand multi-platform](https://github.com/amzn/style-dictionary/tree/main/examples/advanced/multi-brand-multi-platform) example work for you? You wouldn't be defining different dictionary. Its the same dictionary, with the same configs but looped with different source files....