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
I'm not in particular need of this since I'm working more with db.js, but just in examining your nicely modular projects, I thought I'd share a novelty I added to db.js for blocked connections that you might find of use.
Within the db.jsopen request (and the delete one which also has a couple of other browser bug workarounds you may be interested in), you should see a resume property we add to the onblocked error object so that the user can, as per our README open docs, recover from a blocked event with a promise catch followed by a then.
The text was updated successfully, but these errors were encountered:
Sure... If versionchange handlers have already been set up and if they close their own connections, there will be no blocked event, so by using best practice, there shouldn't be too much of a need for this, I think but if one wants to control the behaviors at the point of making the open request, it may come in handy.
Hi,
I'm not in particular need of this since I'm working more with
db.js
, but just in examining your nicely modular projects, I thought I'd share a novelty I added to db.js forblocked
connections that you might find of use.Within the
db.js
open
request (and thedelete
one which also has a couple of other browser bug workarounds you may be interested in), you should see aresume
property we add to theonblocked
error object so that the user can, as per our README open docs, recover from a blocked event with a promisecatch
followed by athen
.The text was updated successfully, but these errors were encountered: