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
Current Behavior
If I specify fetchTimeout in the init method, the timeout only comes into effect when the request fails. If the request is simply slow, due to network latency, the timeout doesn't trigger.
Expected Behavior
The timeout should be triggered when the fetch request is slow.
Steps to Reproduce
Initialize Transifex Native using a fetchTimeout.
Simulate network latency through a proxy or other developer tools. The latency must be longer than the configured timeout.
Observe that translation-fetching continues past the timeout.
Possible Solution
Add a timeout to the axios.Get call.
Possible Implementation
I would use an Axios AbortController with a timeout based on fetchTimeout, as documented on this page: https://axios-http.com/docs/cancellation
The text was updated successfully, but these errors were encountered:
Current Behavior
If I specify
fetchTimeout
in theinit
method, the timeout only comes into effect when the request fails. If the request is simply slow, due to network latency, the timeout doesn't trigger.Expected Behavior
The timeout should be triggered when the fetch request is slow.
Steps to Reproduce
fetchTimeout
.Possible Solution
Add a timeout to the
axios.Get
call.Possible Implementation
I would use an Axios
AbortController
with a timeout based onfetchTimeout
, as documented on this page: https://axios-http.com/docs/cancellationThe text was updated successfully, but these errors were encountered: