You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am investigating if we can use Token Studio at the current company in the iOS project. I was playing with code generation for Swift and unfortunately I wasn't able to get the output in Swift that compiles.
Output in Swift that compiles. Right now the generated code contains many invalid lines of code like:
public class {
public static let colorsBlue100 = #ebf8ff
public static let dimensionXl = 4px * 2 * 2 * 2 * 2
public static let fontWeightsBodyBold = Bold
public static let exampleShadow = [object Object]
public static let fontFamiliesHeading = Inter
}
Version
0.9.1
The text was updated successfully, but these errors were encountered:
We currently by default apply style-dictionary transforms on the transformGroup that are Web specific. You see this in the hex value, font family value, they would work in CSS but not other platforms.
We basically need more input from iOS developers about how these values should work in iOS context, because I am not an iOS developer myself :). I would be happy to add transforms that work for iOS/mobile context, could you elaborate on how values work in iOS for:
typography
border
shadow
color
dimensions
As for the [object Object] and the math expression not getting resolved, not sure why this happens with your tokens, would need to see a reproduction with some tokens and a style-dictionary config / build file.
What happened?
Hi all 👋
I am investigating if we can use Token Studio at the current company in the iOS project. I was playing with code generation for Swift and unfortunately I wasn't able to get the output in Swift that compiles.
Reproduction
ios-swift
ios-swift/class.swift
Here's the link to reproduce the issue.
Expected output
Output in Swift that compiles. Right now the generated code contains many invalid lines of code like:
Version
0.9.1
The text was updated successfully, but these errors were encountered: