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
But I don't know if it's worth it... what would be gained, the Error.code property? That's already deprecated and I'm not sure if anyone uses it for IndexedDB. Anything else?
If there's a compelling use case, then yes please go for it. And also in src/test/web-platform-tests/wpt-env.js replace global.DOMException = Error; with importing that module to the global scope.
fake-indexeddb currently throws exceptions that are
Error
objects, but IndexedDB throwsDOMException
s.Of course, this is a little sticky 'cause fake-indexeddb is on Node, but there seems to be a well-known
DOMException
polyfill that could be used.Seems like an easy change: just modify
src/lib/errors.ts
, right?. I can try to make a PR with your go-ahead.The text was updated successfully, but these errors were encountered: