Modes

[Gabigabor]

It seems, variable modes are not supported. Is it possible to detect the modes as well in the near future?

[guspimentel]

This would be a game changer!

[theisnygaard]

+1
We rely heavily on modes in our current setup and would love for this to be included in the output.

[mcrider]

Yeah, I set this plugin up and integrated it with my repo (and it all worked really nicely) but without support for modes we have no use for it unfortunately. Would be great to get this added.

[JumperPunch]

Is there any update on this?

[ds1]

Hey all!

Would love to better understand how Modes are a part of your workflows, to design their implementation properly.

I appreciate the enthusiasm and will prioritize investigating Modes for the next GitFig version.

If you could tell me your team setup / usage / proposed ideal state, that'd be incredibly helpful!

Thank you!

[mcrider]

Probably something like how tokens studio exports multiple themes, though I forget how they handle theme inheritance. But ignoring inheritance, if the root object in gitfig's export was keyed by mode, each mode would contain all variables. A simple example is dark and light mode -- Gitfig's export would look like

{
 dark: { ... all dark tokens},
 light { ... all light tokens}
}

And I would expect these to be structurally the same (but obviously with different values).