Build Warning: External link https://badges.layer5.io was detected in a Link component

[leecalcote]

Current Behavior

The following warning is emitted when the site is built.

External link https://badges.layer5.io was detected in a Link component. Use the Link component only for internal links. See: https://gatsby.dev/internal-links

Desired Situation

1. Find all references to badges.layer5.io. Ensure they do not produce a warning.
2. Ensure that the component handles both internal and external links properly.
3. Ensure that the component handles both internal and external links properly.

---

Contributor Resources and Handbook

The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.

• 📚 See contributing instructions.
• 🎨 Wireframes and designs for Layer5 site in Figma (open invite)
• 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack.

Join the Layer5 Community by submitting your community member form.

[Jaishree2310]

@leecalcote I would like to work on this issue.

[Tharanishwaran]

@leecalcote I tried to reproduce this warning locally but couldn't find this warning. could you help point me to where you're seeing it? Thanks!

[Ajay-singh1]

@leecalcote We can close this issue now.It has been resolved.

[Jaishree2310]

@Ajay-singh1 It was assigned to me i was working on this issue

[Jaishree2310]

@FaheemOnHub Please work on your issue and check whether the problem is already assigned to someone or not

[FaheemOnHub]

@Jaishree2310
Thank you for bringing this to my attention. While working on my assigned issue #6173, I noticed that the second problem was closely related and could be resolved with the same solution. To ensure consistency across the codebase, I addressed both issues in the same PR.

I apologize for not clarifying this earlier, but I felt it was necessary to make these changes together to maintain consistency.

[Jaishree2310]

@Jaishree2310 Thank you for bringing this to my attention. While working on my assigned issue #6173, I noticed that the second problem was closely related and could be resolved with the same solution. To ensure consistency across the codebase, I addressed both issues in the same PR.

I apologize for not clarifying this earlier, but I felt it was necessary to make these changes together to maintain consistency.

I noticed the same issues that were assigned to you, but I ensured the code was structured in a way that would help you address them easily.

No worries at all—just make sure to take care of this next time. 😊

[Ajay-singh1]

@FaheemOnHub @Jaishree2310 I cannot replicate this warning on my machine.Can you confirm?

[FaheemOnHub]

@Ajay-singh1 the issue is already solved by the pr #6179 and has been merged

[Ajay-singh1]

Thanks @Jaishree2310 for taking interest in working on this issue but I think it has been resolved via #6179.In the meantime you can check out another issues.