Zoë Philipps
Zoë Philipps
@jesseleite I don't believe so.
👋 Hello there! I've written a blog post that references this issue! You can view the applicable excerpt/code snippet here: [The component’s variable name must match its displayName](https://zackphilipps.dev/posts/storybook-csf-mdx-known-issues-typescript-styled-components#the-components-variable-name-must-match-its-displayname---15401) GitHub discussion:...
:+1: This would be nice for people just getting started.
$ node -v v0.10.26 $ npm -v 1.4.4 $ yo -v 1.1.2 Running Mac OS 10.9.1
Lol I am also pretty tied up this week, but I'll let you know if I've taken a crack at it. On Tue, Feb 25, 2014 at 10:59 AM, Romain...
This line is the culprit: https://github.com/amzn/style-dictionary/blob/6182d63765b86b19a83d27eeee227d5b0b9ea4ee/lib/common/formatHelpers/createPropertyFormatter.js#L131 So, it appears that the `asset/swift/literal` transform is not necessary. A workaround is replacing `transformGroup: "ios-swift",` with this: ```js transforms: [ "attribute/cti", "name/cti/camel", "color/UIColorSwift",...
Closing the loop here, I still needed a transform to wrap all strings in `"`, some of which didn't fall within `asset`, `content`, or `font` categories. Here's what I wrote;...
@kadamwhite Is there a workaround for this in the meantime? I'm struggling with this...
The workaround is adding a custom endpoint. 👍
Hey @JonnyBurger, thanks for this. I was able to get it almost working with the changes in #4091. However, now I'm running into this issue, and I have no idea...