You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.
But this actually ends up passing the retry directly to fetch as well, even if this is not a valid option in fetch. It is nice that you can override the retry options per fetch invocation, but it would be good if this was not passed to fetch. This causes errors in combination with the nock test tool, as it will not be able to intercept the call anymore.
Suggestion Solution:
fetch-retry should not pass retry options to fetch. This can be done by removing opts.retry before passing it to fetch.
The text was updated successfully, but these errors were encountered:
Hi there 👋 ,
According to the docs, you may add opts.retry to fetch like this:
But this actually ends up passing the retry directly to fetch as well, even if this is not a valid option in fetch. It is nice that you can override the retry options per fetch invocation, but it would be good if this was not passed to fetch. This causes errors in combination with the nock test tool, as it will not be able to intercept the call anymore.
Suggestion Solution:
fetch-retry should not pass retry options to fetch. This can be done by removing
opts.retry
before passing it to fetch.The text was updated successfully, but these errors were encountered: