Skip to content

feat: add redirect request option #636

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.

Sign up for GitHub

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

Jump to bottom
Merged
wolfy1339 merged 9 commits into from
Apr 9, 2024
Merged

feat: add redirect request option #636

wolfy1339 merged 9 commits into from
Apr 9, 2024

Conversation

@mitchcapper
Copy link
Contributor

@mitchcapper mitchcapper commented Sep 23, 2023 •
edited by wolfy1339
Loading

Resolves #635

Before the change?

  • Setting {request: {redirect:"value"} } does nothing

After the change?

  • Setting the redirect property on the request sub property is properly passed to fetch for the request.

Pull request checklist

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Is it breaking? not really, this is the desired behavior, I can't imagine anyone has a valid use case to set the redirect option and have it ignored.

Please see our docs on breaking changes to help!

  • Yes
  • No