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
Trying to publish a sample component and I’m getting the following error for multiple components (not the component I’m trying to publish, but colocated components in the parent directory:
Error parsing story /Users/ramy/GitHub/metal-design-system/packages/component-library/src/components/Banner/Banner.stories.tsx: ParserError: "url" property not found in"design" object in story metadata
-> /Users/ramy/GitHub/metal-design-system/packages/component-library/src/components/Banner/Banner.stories.tsx:154:11
The url prop is present and filled in the story file, but it’s pointing to an object in a different file, like so (we keep all the links in one place for Storybook for easier updating):
Guessing this is some kind of conflict with the design add-on?
It’s also unclear to me why it’s trying to do anything with those files since I don’t have a .figma.tsx file for those. I’m only trying to publish one component but it’s returning this error for many unrelated components.
Happy to provide more details here!
The text was updated successfully, but these errors were encountered:
Thanks for reaching out. The storybook parser checks for any usage of design.url in story files, but, unfortunately, we only parse strings for the url field at the moment.
Trying to
publish
a sample component and I’m getting the following error for multiple components (not the component I’m trying to publish, but colocated components in the parent directory:The
url
prop is present and filled in the story file, but it’s pointing to an object in a different file, like so (we keep all the links in one place for Storybook for easier updating):Guessing this is some kind of conflict with the design add-on?
It’s also unclear to me why it’s trying to do anything with those files since I don’t have a
.figma.tsx
file for those. I’m only trying to publish one component but it’s returning this error for many unrelated components.Happy to provide more details here!
The text was updated successfully, but these errors were encountered: