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
After launching props table support in @storybook/addon-docs, we've found an impossibly large number of cases to handle (nearly 100 issues so far), many of which correspond to failures in an underlying library.
To properly support prop tables, we need a proper testing and bug reporting strategy. I propose:
Test suites for each supported framework (react, vue, angular, ember, wc)
Snapshot the output of the underlying library
Snapshot the output of our props extraction
Display the resulting prop table in storybook
Process for filing issues
Sweep of existing issues to add them or de-dupe them
This will also help as we move to react-docgen for typescript prop tables in 6.0. #9837
The text was updated successfully, but these errors were encountered:
After launching props table support in
@storybook/addon-docs
, we've found an impossibly large number of cases to handle (nearly 100 issues so far), many of which correspond to failures in an underlying library.To properly support prop tables, we need a proper testing and bug reporting strategy. I propose:
This will also help as we move to
react-docgen
for typescript prop tables in 6.0. #9837The text was updated successfully, but these errors were encountered: