-
Notifications
You must be signed in to change notification settings - Fork 11
feat: Add support for advanced redirect types #117
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
Conversation
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.
Nice work! I didn't realise they'd done a blog about it. We should post something about this, even if it's just an announcement in the forums
Ah maybe blog post isn't the right term - just a post in their Support's "How to Guide". I couldn't find any similar examples in their official docs. |
Oh yeah. Looks like that's their cloud support guide, because it's not in the main OSS product |
`Language`, | ||
`Country`, |
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.
This was a breaking change and it should have been introduced in a major bump. All the redirects were possible previously, but the change broke our delpoyment. I do agree that the conditions
key may be more suitable, but let's just be cautious with the breaking changes in the future.
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.
This PR adds support for advanced redirect types in gatsby, as mentioned in their support blog post
I've also added a snapshot test to ensure that each of these types of redirects are being output to the _redirects file properly.
Closes: #93