generate-arg-types: Allow multiple exports in component files #1953
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.
Description
Allow multiple exports in components. Most radix components will look like
export const Tooltip = TooltipPrimitive.Root;
The others would be a simpe wrappers over radix with just type changes like like `Omit<TriggerProps, "className">
It's too much to create for each sucj export a standalone file.
After this PR following will work.
Generated exports in case of multiple entries are
In case of single export previous behaviour is preserved for now, but should be changed IMO in the future PRs
Known bugs
Until this merged we should not use displayName (have no idea why we use it at all) in files with multiple exports
styleguidist/react-docgen-typescript#449
As of now will add comments
Steps for reproduction
Code Review
Before requesting a review
Before merging
.env.example
and thebuilder/env-check.js
if mandatory