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.
Hey! Thanks for a great tool!
I'm building a dashboard for tracking components usages of my company's private UI kit.
And I'm having an issue when an import of a default export of the same component using different names results in the different components in the report:
will end up with:
Since the module name is the only way to uniquely identify components with default export I can suggest only few ideas:
This PR allows users to choose their own naming strategy by providing a
importType
field along with other import data.It can be used inside
getComponentName
callback or duringprocessor
step by merging data for components with the same module name andimportType === 'ImportDefaultSpecifier'