chore: Remove TypistEditor
reference from Storybook
#703
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
From Storybook's blog post about Storybook 8:
But this change presented a problem for us...
I asked about it here, and the suggested solution was to fallback to the previous default for component analysis:
react-docgen-typescript
. However, this does not seem to be working as expected:So, for the time being, we are reverting to
react-docgen
, and hiding theTypistEditor
component reference from Storybook. This way we can continue to run Storybook locally, at the expense of not showing theTypistEditor
component arguments table (with types and descriptions). As a workaround, consumers can rely on the JSDoc itself (it's the same information anyway).PR Checklist