Closed mitchcapper closed 5 months ago
The option was removed in #599 / #612
We removed all custom options, in favour of users using wrapping fetch with their options
Do we want to reintroduce it though? @gr2m
It's not a custom option though? I'm not quite sure if we discussed removing the redirect
option explicitly, I thought that's one we wanted to keep passing through?
After discussion in #635 I did think this was the desired current behavior so meant to close this PR. I am happy to add a test case to ensure this option works if it is desired for this feature to be re-introduced.
@wolfy1339 can you recall specifically why we removed the redirect
option, given that it's a native fetch
option? It might be related to the fact that (I think) it behaves differently in browsers and backend environments due to CORS restrictions that only apply in browsers?
I don't know.
It's odd to me that we left signal
but removed request
.
I think for now I would leave it as is as we have a working workaround. We can revisit the discussion as more folks experience the lack of redirect
and other native fetch options as friction
:tada: This PR is included in version 9.1.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Resolves #635
Before the change?
After the change?
Pull request checklist
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!