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
The declarations and parent properties on the docgen property object appear to be missing (thus not filtered by the default method) in later versions of typescript (after v5.0.4). For example, a docgen property object when working as expected:
After some exploration, (this part of the source code) where the declarations are populated for each property do not seem to be working after v5.1.3. The thread appears to lead to typescript itself (ts.Symbol) has changed.
I just want to add that I'm seeing this situation in a project on TypeScript 4.9.5, so I don't know if this is necessarily related to TypeScript version (at least not the major version update). In my investigations, I came to believe that this might be related to the tsconfig that is used when running the parser - perhaps which types are considered to be "in the program" will affect whether those types are correctly populated? I'm stabbing in the dark here because my knowledge of the TS compiler is limited.
Having similar issue to Garden components - I'm doing custom library and what to do Storybook for components, importing them as dependency from package (import ... from 'my-library-name'). It doesn't display any properties from these components, but it fixes if I import them directly by path, without package name (import .... from '../../my-library/src/components/').
The
declarations
andparent
properties on the docgen property object appear to be missing (thus not filtered by the default method) in later versions oftypescript
(after v5.0.4
). For example, a docgen property object when working as expected:compared to:
After some exploration, (this part of the source code) where the declarations are populated for each property do not seem to be working after v5.1.3. The thread appears to lead to
typescript
itself (ts.Symbol
) has changed.See previous issue.
The text was updated successfully, but these errors were encountered: