Fix: Open project links in new tab and resolved invalid <Link> with <a> child error. #244
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
What does this PR do?
target="_blank"to the anchor tags.<a>in<Link>error by removing the nested<a>tag and using thepassHrefprop correctly in thenext/linkcomponent.Why are these changes necessary?
<a>in<Link>error was causing a server-side rendering issue, which needed to be fixed for the website to function correctly.How does it address the issue?
target="_blank"attribute was added to the anchor tags within the project cards, ensuring links open in a new tab.<a>tag was removed from within theLinkcomponent to follow Next.js best practices, preventing the error.Additional Context