T
13

Pro tip: double check your token variables before pushing to production

I spent last Sunday rebuilding a whole component library because someone on the team accidentally swapped the primary and secondary color tokens in our Figma file. It looked fine on their screen but broke the entire button system on our staging site. Anyone else had a simple variable mixup cascade into a nightmare?
2 comments

Log in to join the discussion

Log In
2 Comments
theabennett
Wait, so someone swapped primary and secondary and nobody caught it until the whole button system broke? Oh man, that's brutal. I once had a junior dev accidentally set our entire error state color to "hot pink" instead of the actual error red - took us three days to figure out why our alerts looked like Valentine's Day cards. A color token mixup is honestly one of those things that sounds dumb in retrospect but can absolutely wreck your whole UI. Hope your team added some automated checks after that Sunday rebuild. Take it as a lesson learned the hard way, right?
1
the_jason
the_jason2d ago
Three days to fix a color seems a bit much doesn't it.
4