Multiple Export Definitions Error

Open
#393 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
react, typescript
Domain
tooling

Research direction

Start by reproducing the failure with the buildDocs script and the resolver option findAllExportedComponentDefinitions. Inspect resolver/findExportedComponentDefinition.js around line 107 and compare the behavior with the related issue #213. Done means multiple Redux-connected component exports no longer produce the multiple-definitions error when the alternate resolver is selected.

Written by the indexing model from the issue text.

Description

I'm getting the following error when I run my buildDocs script:

.../resolver/findExportedComponentDefinition.js:107
throw new Error(ERROR_MULTIPLE_DEFINITIONS)

This error still occurs even after I add the resolver option:

--resolver  findAllExportedComponentDefinitions

I have seen a previous issue with the similar problem here: https://github.com/reactjs/react-docgen/issues/213

I have multiple exports for Redux connected components for ease of testing.

And as more background info, my application utilizes TypeScript, React, and Redux. I am using react-docgen v5.0.0-beta.1

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.