reactjs / reactjs/react-docgen
Third party typescript components not getting parsed
Open
Nobody has claimed this yet.
improvement
- Dominant language
- TypeScript
- Stars
- 3.8k
- Forks
- 316
- Avg merge
- 5h 7m
- Merged PRs (30d)
- 4
Description
This is coming from https://github.com/styleguidist/react-styleguidist/issues/1508
Previously with react-docgen-typescript, third party component props are getting parsed and visible with the extended component. But with react-docgen v5, they are not getting listed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue links styleguidist/react-styleguidist#1508 and names react-docgen-typescript plus react-docgen v5; start by reading that linked report and comparing their handling of third-party component props. Done means props from third-party TypeScript components are parsed and listed on the extended component.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100