-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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): handle case of changing page path casing on case-insensitive fs #31071
Merged
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
gatsbot
bot
added
the
status: triage needed
Issue or pull request that need to be triaged and assigned to a reviewer
label
Apr 27, 2021
pieh
added
topic: build
Related to the Gatsby build process
and removed
status: triage needed
Issue or pull request that need to be triaged and assigned to a reviewer
labels
Apr 27, 2021
vladar
reviewed
Apr 27, 2021
vladar
approved these changes
Apr 27, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! 👍
vladar
pushed a commit
that referenced
this pull request
Apr 27, 2021
…tive fs (#31071) (#31082) * fix(gatsby): handle case of changing page path casing on case-insensitive fs * figure out if platform is case insenstive once and not for every page separately * add tests for casing ... cases (cherry picked from commit 940eddf) Co-authored-by: Michal Piechowiak <misiek.piechowiak@gmail.com>
pragmaticpat
pushed a commit
to pragmaticpat/gatsby
that referenced
this pull request
Apr 28, 2022
…tive fs (gatsbyjs#31071) * fix(gatsby): handle case of changing page path casing on case-insensitive fs * figure out if platform is case insenstive once and not for every page separately * add tests for casing ... cases
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.
Description
On Windows and MacOs if you change casing of page path it results in page being generated and then deleted.
Consider scenario of creating
/TEST/
page and then inonCreatePage
adjust page path to lower case which results in/test/
page. What currently happen is that/test/
is generated and/TEST/
is scheduled for deletion. In case insensitive filesystems it means we will delete same files we just created.Related Issues
fixes #31055