refactor: remove redundant fragment wrapping a single child #1054 #1144
+1
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
KartikSethi21
requested review from
magicmatatjahu,
fmvilas,
asyncapi-bot-eve and
AceTheCreator
as code owners
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
|
KartikSethi21
changed the title
KartikSethi21
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request removes an unnecessary React fragment (<>...</>) that wraps a single child component (), improving the code's clarity and alignment with best practices. Since a fragment is only needed for multiple children, removing it ensures a cleaner and more efficient structure.
Additionally, this change contributes to maintaining a React 18-friendly codebase by reducing unnecessary wrappers.
Changes proposed in this pull request:
Removed redundant fragment around the component.
Ensured compatibility with React 18 by simplifying component structure.
Related Issue(s)
Fixes #1054
Contribution Checklist
Followed contributing guidelines and recommended Git workflow.
Tested changes and verified no impact on existing functionality.
Updated relevant documentation if necessary.