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 was archived by the owner on Jul 10, 2024. It is now read-only.
I noticed that the Option "requests" is ignored completeley.
In offline.js, requests is not in the variable defaultOptions, what means in requests.js (Line 65) the code Offline.getOption('requests') returns undefined and the condition is true.
if (Offline.getOption('requests') !== false) {
Offline.on('confirmed-up', function() {
if (waitingOnConfirm) {
waitingOnConfirm = false;
return clear();
}
});
Offline.on('up', flush);
This whole code is executed directly after loading the javascript file.
A user has no possibility to enable or disable the "requests"-Feature, because when the options are set in code programmatically, the events for doing the requests are already binded.
The text was updated successfully, but these errors were encountered:
I'm having this exact problem. Because of my app design, I have to send a call to persist all changes to server. When "requests" is enabled in OfflineJs, it causes all my changes to be duplicated.
Life would be so much easier if this feature could really be disabled as it says is possible in the documentation.
Hello,
I noticed that the Option "requests" is ignored completeley.
In offline.js, requests is not in the variable defaultOptions, what means in requests.js (Line 65) the code Offline.getOption('requests') returns undefined and the condition is true.
This whole code is executed directly after loading the javascript file.
A user has no possibility to enable or disable the "requests"-Feature, because when the options are set in code programmatically, the events for doing the requests are already binded.
The text was updated successfully, but these errors were encountered: