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
The goal is to introduce an onAbort interceptor in the fetchff plugin to handle request abort scenarios. This interceptor will allow developers to define custom logic that executes when a request is aborted (e.g., due to a user action or timeout).
Why?
The fetchff plugin supports request cancellation and timeouts, but there is currently no dedicated hook to handle abort-specific logic. Having an onAbort interceptor will improve flexibility and control, especially in cases where different actions need to be taken based on whether a request was aborted or completed normally.
Expected Behavior:
The onAbort interceptor should trigger when a request is aborted manually and not due to a timeout.
It should receive the request configuration and other relevant details, similar to existing interceptors like onRequest and onResponse.
This will not affect normal cancellation behavior but provide an additional opportunity for handling abort-specific logic.
The text was updated successfully, but these errors were encountered:
The goal is to introduce an onAbort interceptor in the fetchff plugin to handle request abort scenarios. This interceptor will allow developers to define custom logic that executes when a request is aborted (e.g., due to a user action or timeout).
Why?
The fetchff plugin supports request cancellation and timeouts, but there is currently no dedicated hook to handle abort-specific logic. Having an onAbort interceptor will improve flexibility and control, especially in cases where different actions need to be taken based on whether a request was aborted or completed normally.
Expected Behavior:
The onAbort interceptor should trigger when a request is aborted manually and not due to a timeout.
It should receive the request configuration and other relevant details, similar to existing interceptors like onRequest and onResponse.
This will not affect normal cancellation behavior but provide an additional opportunity for handling abort-specific logic.
The text was updated successfully, but these errors were encountered: