Remove "unnamed" from font-family, font-size, character-spacing and text-transform design tokens until we are able to name them
The design variables list is filled with "unnamed" variables that we can't name. It creates an extra step for developers to clean up the list given to them after download.
Peter Wise commented
Shweta Dave commented
This is very very very critical and imp for design systems and developers are looking for alignment in design and coded component so please this has to be updated ASAP.
Please implement this as soon as possible. This is a critical step that is a key element to unite the XD software and interactive design with the developers, otherwise, developers would possibly be less likely to work with this and would prefer a competitor software instead.
Cheryl Walters commented
It amazes me how little votes this has received. Token design is difficult for inexperienced developers, and reading the produced code is difficult https://idlebreakout.io
Christoffer Björkskog commented
Agree - while onboarding devs to a design file and walking through the handoff, this makes it appear very sloppy and unfinished.
Jack Kidman commented
I can't believe this has so few votes.
It's confusing for devs new to design tokens and confusing to read when reviewing the generated code.
Mike M commented
Yes, this is annoying. Please fix this ideally, but remove broken variable names otherwise. I had a developer ask me about this. Abeit they should be able to load web fonts themselves without generated code, but it just makes my life harder to explain that they shouldn't really follow the CSS generated by Adobe XD because it's unreliable and to take it with a grain of salt.
This is absolutely awful.
The more I use XD, the more I find ridiculous problems and issues that should have been solved when it was still in beta testing.
Things like this make is simply unusable for professional teams.
Zach Bruce commented
Just looked into possibly switching to Adobe XD from Zeplin for developer handoff and it's things like this that give us a solid "no" for an answer.
It looks awful and my OCD is getting worse every time I see ”--unnamed” and cant do anything about it... please fix
Eugen Pflüger commented
Sharing like this is useless. It looks like a bug all the time.
I mean "unnamed"...wth...this is such a bad bug and would be so easy to fix.
I made a new document to test this out and with adding just one font style and one color and putting one word using those two on the canvas. This is the CSS created:
/* Colors: */
/* Font/text values */
--unnamed-font-family-open-sans: Open Sans;
/* Character Styles */
Please get rid of the useless wording or grant us the power to change it to something more handoff friendly. :)
I'm trying to convince people at our company to switch fully switch to adobe for development and marketing purposes ... Its hard to convince developer leads that this solution is superior when the CSS looks like this. Any idea how to bypass this?
Rich Prior commented
I can't believe this has so few votes. It's confusing for devs new to design tokens and confusing to read when reviewing the generated code.