-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement support for more text style properties? #18
Comments
I've created a PR for at least |
Mind you, I discovered that fontWeights could be more versatile. Some names, as derived from Google Fonts, are not supported. Examples:
I changed this in More details can be found in the update for |
Thank you @JeroenRoodIHS |
Thanks! I just realized that I wasn't careful enough with the font weights. I made two oversights. My sincere apologies. Invalid inputFontWeight heuristics
Missing heuristics for mapping all kinds of font weight variationsThe font-weights with Example:
I know it is probably an impossible effort to map all possible fontWeight keywords used for any font out there. But maybe we can use the mapping as defined on MDN, and apply the casing/dash heuristics on top of that: Something along the lines of:
This suggestion seems to work, after some tweaking of The function would look like this:
This is how I tested it:
|
Here's the PR for correcting the oversights: #20 |
Hi! As I was working my way through processing tokens for text styles, I learned that some properties as provided by the Figma Plugin API
TextStyle
object are not yet supported. I am talking about the following:textDecoration
(link)textCase
(link)There are other properties, of which I am unsure whether or not they would be useful:
leadingTrim
(link)paragraphIndent
(link)paragraphSpacing
(link)listSpacing
(link)hangingPunctuation
(link)hangingList
(link)I think I can safely implement support for
textDecoration
andtextCase
and create a PR. Is that okay?As for the others, I would like to know what your stance is on this.
The text was updated successfully, but these errors were encountered: