Dependency detection

Open
#82 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
react, typescript
Domain
documentation, tooling

Research direction

No files, tests, or entry points are named in the issue. Start by locating the JSX parsing and component metadata extraction paths in the repository, then determine how dependency data is represented. Done means reliably identifying component tag names while excluding native tags and exposing them in the generated dependency list.

Written by the indexing model from the issue text.

Description

custom-handler question

Hi, wondered if it is possible to parse the jsx and obtain all Tag names (maybe exclude native tags) to form the dependency list for the component.

Cheers :)

Dominant language
TypeScript
Stars
3.8k
Forks
316
Avg merge
3h 28m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from reactjs/react-docgen

All issues in reactjs/react-docgen

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.