Make `args` and `argTypes` available in `meta.json` about ladle

[tajo]

Closing, since this is not technically feasible. Anyway, we might have some better & analyzable controls API in the future.

[tajo]

Good question, I would like to use something like this too. The issue is that args / argTypes are not statically analyzable and they need to be executed (if we want to stay Storybook compatible). So you can't just simply export them through meta.json. There was a similar discussion about this here: #127 (comment)

I see two solutions:

• propose a new (different) format for controls that will be strictly static
• add some argStatic mode that would attempt to statically analyze args/argTypes and throw an error if not possible Your example would work just fine:

Index.argTypes = {
  variant: {
    options: ["default", "primary", "danger"],
    control: { type: "inline-radio" },
  }
};

however, this would fail

const variant = {
  options: ["default", "primary", "danger"],
  control: { type: "inline-radio" },
}
Index.argTypes = { variant };

Does it make sense?

[madebyherzblut]

Thanks for the link @tajo–I always assumed args/argTypes are statically analyzable as well and it would be easy to export them. Are there any use cases where those are not strictly static?

Personally, I think the CSF compatibility of Ladle is a great feature and it is worth the wait until a mutual standard has been set.

[tajo]

Are there any use cases where those are not strictly static?

They could be static, it's all simple arrays/objects but it's not been enforced in Storybook ecosystem (same with story titles, which Ladle actually strictly enforces and diverges from Storybook on that since it's critical for code-splitting and other features). Typically, devs assign args into a variable so they can spread it out over multiple stories.