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

fix(gatsby): Decode base path in runtime #30682

Merged
merged 5 commits into from
Apr 12, 2021

Conversation

herecydev
Copy link
Contributor

Description

Decodes the base_prefix as this could also be encoded.

Related Issues

Fixes #30533

@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Apr 5, 2021
@LekoArts LekoArts added topic: core Relates to Gatsby's core (e.g. page loading, reporter, state machine) and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Apr 6, 2021
@herecydev
Copy link
Contributor Author

I'm pretty sure the test failures aren't a cause of the changes (other PRs seem to be failing with the same results)

@vladar
Copy link
Contributor

vladar commented Apr 12, 2021

I suspect it could be a breaking change. Can you add another test case for prefix /test/blog?

@herecydev
Copy link
Contributor Author

I suspect it could be a breaking change. Can you add another test case for prefix /test/blog?

Of course, I'll get on that ASAP

@herecydev
Copy link
Contributor Author

Screenshot 2021-04-12 151640

@vladar was that what you had in mind? They're all passing fine

Copy link
Contributor

@vladar vladar left a comment

Choose a reason for hiding this comment

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

Actually, I've looked into it a bit more and this seems to be a safe change. Thanks 👍

@vladar vladar changed the title Decode base path fix(gatsby): Decode base path in runtime Apr 12, 2021
@vladar vladar merged commit 304e585 into gatsbyjs:master Apr 12, 2021
moonmeister added a commit that referenced this pull request Apr 14, 2021
* master: (183 commits)
  chore(gatsby-plugin-image): Remove version note (#30758)
  docs: retire 'How to Create Pages' stub and Recipes landing page (#30842)
  chore(docs): Fix typo (#30858)
  docs: fix invalid mailto links in 3.3 release notes (#30862)
  docs: release notes for 3.3 (#30837)
  fix(gatsby-source-wordpress): invalidate less queries during previews (#30770)
  fix(gatsby-starter-wordpress-blog): Fix altText (#30832)
  feat(contentful): warn users when using restricted content type names (#30715)
  Refactor: using-contentful to use gatsby-plugin-image exclusively (#30717)
  chore(gatsby-plugin-styled-components): Remove breaking changes section (#30806)
  fix(gatsby): webpack warnings are no longer in object format by default (#30801)
  fix(gatsby): Decode base path in runtime (#30682)
  fix(gatsby): "Cannot find module 'babel-preset-gatsby'" error (#30813)
  handle plugin parentDir resolution in resolvePlugin() (#30812)
  Port using-gatsby-image site to image plugin (#28489)
  fix(gatsby-source-contentful): De-dupe type names (#30834)
  feat(gatsby): Add aggregation resolvers (#30789)
  fix(gatsby-core-utils): fetch-remote-file download failure when missing content-length header (#30810)
  fix(renovate): add breaking minor updates to major updates list (#30676)
  chore(docs): Update migration guide for plugins that support both v2 & v3 (#30825)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: core Relates to Gatsby's core (e.g. page loading, reporter, state machine)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Loader does not decode pathPrefix correctly
3 participants