Remove restrictions on props passed to components

[bebbi]

For a visualization graph I am passing a d3 graph structure with cycles.

Storybook complains that it cannot deal with a prop with cycles.

Yes, it's easy enough to work around that issue by wrapping the graph in a function prop that returns it, but it feels awkward to change the component signature to accommodate storybook.

Wouldn't it be important for Storybook to support any kind of props?

[phated]

Good question!

Storybook communicates between your component preview and the "manager" (UI and addons surrounding the components) using postMessage. That method doesn't allow JS objects to be sent, so your props need to be stringified before being sent and JSON.stringify doesn't support cycles.

[bebbi]

Thanks for the info @phated. Perhaps, since it can accept functions, it might be able to transparently wrap/unwrap props with cycles into functions to circumvent that limitation.

[phated]

@bebbi Hmmm, I was just looking at the function caveats in https://github.com/storybookjs/telejson and the behavior seems a bit different than what you'd expect with cycles (specifically the lazy eval and performance implications). 🤔