-
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): don't break builds when using features unsupported by adapter #38520
Merged
pieh
merged 1 commit into
master
from
dont-fail-the-build-if-adapter-doesnt-support-a-feature
Sep 5, 2023
Merged
fix(gatsby): don't break builds when using features unsupported by adapter #38520
pieh
merged 1 commit into
master
from
dont-fail-the-build-if-adapter-doesnt-support-a-feature
Sep 5, 2023
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
Sep 5, 2023
pieh
removed
the
status: triage needed
Issue or pull request that need to be triaged and assigned to a reviewer
label
Sep 5, 2023
MarcL
approved these changes
Sep 5, 2023
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.
Thanks for the quick fix.
pieh
deleted the
dont-fail-the-build-if-adapter-doesnt-support-a-feature
branch
September 5, 2023 11:14
2 tasks
This was referenced Sep 26, 2023
This was referenced Nov 22, 2023
This was referenced Nov 29, 2023
This was referenced Dec 7, 2023
This was referenced Dec 19, 2023
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
With release of adapters we introduced a way for adapters to report back if they support handling of
pathPrefix
andtrailingSlash
options. In that release we made gatsby break builds if user options were unsupported by adapter as it did make sense to not allow potentially faulty deploys.However because this wasn't major version bump it can be deemed as breaking change (especially if previously used deployment plugin didn't hard break on their own), so this change stops build failures and instead just prints a warning.
Users might be able to add their own support in some cases (in particular path prefix could be supported on Netlify with https://answers.netlify.com/t/deploy-gatsby-site-to-netlify-with-prefix-paths/1267/6 at least for static assets, but that wouldn't work for DSG/SSR tho, so it's also not full support), so this change unblocks thoes cases.
Documentation
Tests
Related Issues
Fixes: https://github.com/netlify/pillar-support/issues/720