-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[addon/knobs] JSX Support #1580
Comments
Can you elaborate? |
I updated the issue description 😉 |
The most obvious use case is a component that expects children |
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. We do try to do some housekeeping every once in a while so inactive issues will get closed after 90 days. Thanks! |
I think I'll add babel parsing to object knob after #1460 gets merged. But we need to find a way to prevent XSS first |
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 60 days. Thanks! |
Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook! |
It would be great if the knobs add-on had the ability to input simple JSX (
img
tags, etc.).For instance: I have a coponent. One of its attributes is an object containing JSX, in this case an
img
tag. I'd like to be able to modify theimg
tag from the Knobs panel in Storybook. However, it seems that in order to do so, I'd need to have a function similar to for instance object but that allows to pass JSX.The text was updated successfully, but these errors were encountered: