Skip to content
This repository has been archived by the owner on Oct 26, 2023. It is now read-only.

DEVHUB-220: Relative Link Fix #508

Merged
merged 3 commits into from
Sep 15, 2020
Merged

DEVHUB-220: Relative Link Fix #508

merged 3 commits into from
Sep 15, 2020

Conversation

jestapinski
Copy link
Contributor

@jestapinski jestapinski commented Sep 15, 2020

Linked Issue
Broken Series in Prod
Staging Link to Series Article
Staging Link to Article with Related Articles (just to confirm it still works)

Recently we updated Gatsby to v2.22.11 to v2.24. In 2.22.17 they changed the Link behavior so any paths without a leading slash are now interpreted as relative 🤦

This PR adds a check to the Link to add a leading slash should it not exist.

To Verify:

  • Check out the series at the bottom of the provided article in prod and see how the link is being interpreted as relative
  • Check out the staging link and ensure it is not
  • Also poke around to see if this is happening elsewhere!

@@ -6,7 +6,7 @@ exports[`renders correctly 1`] = `
id="create-an-administrative-username-and-password"
>
<a
class="e1hiqreu0 css-tk4bib-StyledLink-PermaLink eygprlc0"
class="e1hiqreu0 css-b5zgq1-StyledLink-PermaLink eygprlc0"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure why these were updated but seems harmless

@jestapinski
Copy link
Contributor Author

Thanks!

@jestapinski jestapinski merged commit 9fb4d51 into staging Sep 15, 2020
@jestapinski jestapinski deleted the js/relative-link-fix branch September 15, 2020 21:08
jestapinski added a commit that referenced this pull request Sep 15, 2020
staging --> master DEVHUB-220: Relative Link Fix (#508)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants