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
Describe the bug
Addon-docs PropTable is not working correctly in production. The table is correct in development but after deploying to Netlify, it shows only those props which are common to propTypes and defaultProps. Also, the description column shows unknown. The deployed site is here: https://rnds.netlify.com
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 30 days. Thanks!
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 30 days. Thanks!
Describe the bug
Addon-docs PropTable is not working correctly in production. The table is correct in development but after deploying to Netlify, it shows only those props which are common to
propTypes
anddefaultProps
. Also, the description column showsunknown
. The deployed site is here: https://rnds.netlify.comTo Reproduce
Steps to reproduce the behavior:
There is no error log. StoryBook is compiling without error. The PropTable is not working as expected in production.
Expected behavior
https://github.com/iamshadmirza/react-native-design-system
Screenshots
This is in development:
This is after deploying to Netlify or GitHub pages.
Code snippets
To run storybook in development:
To create build:
Additional context
Modules used
The text was updated successfully, but these errors were encountered: