Fix Incorrect JSX Syntax in Knight Component Example#3647
Open
mrbadri wants to merge 1 commit intoreact-dnd:mainfrom
Open
Fix Incorrect JSX Syntax in Knight Component Example#3647mrbadri wants to merge 1 commit intoreact-dnd:mainfrom
mrbadri wants to merge 1 commit intoreact-dnd:mainfrom
Conversation
pieralukasz
approved these changes
Dec 7, 2024
Author
|
Hi @darthtrevino Could you please take a look at this PR when you have a moment? |
Collaborator
Author
Hi @pieralukasz, thank you so much for reviewing my PR! I really appreciate it, and I’ve got it. |
|
Hey, any updates? |
Author
|
Hi @darthtrevino, hope you’re doing well! Could you please review my pull request? |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fix Incorrect JSX Syntax in Knight Component Example
This PR fixes an issue with the JSX syntax in the Knight component example provided in the documentation. The problem was caused by a misplaced closing parenthesis in the return block, which was breaking the component's functionality.
Changes:
Issue:
Closes #3646