Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue: Invalid <Link> Usage with <a> Child #176

Open
isid555 opened this issue Aug 6, 2024 · 9 comments
Open

Issue: Invalid <Link> Usage with <a> Child #176

isid555 opened this issue Aug 6, 2024 · 9 comments

Comments

@isid555
Copy link

isid555 commented Aug 6, 2024

Description

I encountered an error related to the usage of the component in my Next.js project. The error message is as follows:
Screenshot 2024-08-06 111236

Problem

The error occurs when using the component with an tag as a child. According to the latest Next.js documentation, the component now internally handles the tag, and using an tag inside is no longer supported.

Solution

To resolve this issue, the tag should be removed from inside the component. The component should directly handle the styling and attributes.

Impact

This change is necessary to adhere to the latest Next.js guidelines, which streamline the link handling process and prevent issues related to duplicate elements and styling conflicts.

@YashSherla
Copy link

can i attempt

@Vegadjay
Copy link

Vegadjay commented Aug 6, 2024

@isid555
Remove anchor tag from this link componant
image

@isid555
Copy link
Author

isid555 commented Aug 6, 2024

@Vegadjay

My commit is working ,but it's not merged with the actual repo yet
image

@Vegadjay
Copy link

Vegadjay commented Aug 7, 2024

@isid555 Great, I think it's unsolved.

@Tanushmaurya018
Copy link

Hey @Vegadjay,

Summary of Changes

  • Fixed the usage of <Link> with <a> as a child in the [file/path].
  • Improved the code by [mention any specific changes].

Please review, and let me know if further adjustments are needed.

@Tanushmaurya018
Copy link

Hey @Vegadjay , I’m currently working on additional fixes that depend on this PR being merged. It would be great if you could review and merge it when you have a moment. I believe it will streamline the ongoing work. Thanks for your attention to this!

@Vegadjay
Copy link

@Tanushmaurya018 Is your pr merged ?

@Tanushmaurya018
Copy link

@Vegadjay nope

@Vegadjay
Copy link

@Tanushmaurya018 Why this repo is not merge any one pr ???

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants