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
Here is the sample code.
And try pushing the 'fire' button in your browser twice.
If the server returns some error (e.g. 401), you will see 'failed' in console at the first time. But the second time, you will see 'success' and 'undefined' in console without communicating with the server.
Oooh interesting. I think the issue is that we only check whether records are empty before triggering the fetch, but these records are in error. I have some ideas.
Here is the sample code.
And try pushing the 'fire' button in your browser twice.
If the server returns some error (e.g. 401), you will see 'failed' in console at the first time. But the second time, you will see 'success' and 'undefined' in console without communicating with the server.
Is it a bug?
The text was updated successfully, but these errors were encountered: