Nicolas C.

@chicoxyzzy ok ! I started with a PR, but I shied away :) I'll take another PR as example, and should be able to provide a proper test.

whoa, lost a few hours trying to figure out why it was not working for my use case, and it really looked like it wasn't consuming my stream properly. thanks...

Well I don't know the extent of tailwind colors configuration complexity, but if I could import colors in a format compatible with tailwind colors configuration it would certainly to, as...

After reflection maybe we could try to skip the config import add do a mix & match of using [colors alias](https://www.figma.com/plugin-docs/api/VariableAlias/) of the [boundVariables](https://www.figma.com/plugin-docs/api/Paint/#solidpaint) and fallback to bracket syntax (`[color:#994455]`)...

It looks like I greedily would like two feature, the one you describe "round to tailwind colors" to be able to disable it, and another "colors alias", that would use...

Yes exactly, to be of use, this alias feature requires to add the colors to tailwind, either manually or exported from figma, eg by using [such a plugin](https://www.figma.com/community/plugin/1246272456438744360/tw-styles)

> If I made only the "disable color rounding" would you be happy already? 🥺 Yes I think it would be a good feature to have. I tried to experiment...

Note: it seem that only the lingui json format has support for the obsolete flag, I hope depending on it for the tests is not a issue

Ok I must have missed something on my first pass, I'll get right away now that I have the json version set up

Ok, note, we previously had an issue specific to the json files where a `"obsolete": true` was added to translations with partial extract, which does not happen with .po files...