Components: move displayName assignment to top-level files #64793
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.
What?
As discussed in #64613 (comment), this PR tweaks how the
displayName
is assigned to each sub-component.Previously, each
displayName
assignment was performed in the sub-component files — this PR moves the assignments to the top-level file.Why?
Since assigning a
displayName
to sub-components is a consequence of how we're building and exporting our composite components, moving the assignment closer to where the exported object is built just makes sense.How?
Moved the assignments across files, updated the CONTRIBUTING guidelines accordingly.
Testing Instructions
This PR has no runtime changes
Composite
andDropdownMenuV2
subcomponents are named as expected in React Dev Tools and Storybook code snippets