Update indexeddbshim to version 3.0.0 🚀 #92
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
indexeddbshim just published its new version 3.0.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of indexeddbshim.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
The new version differs by 362 commits .
f5f7a8e- Bump to version 3.0.0, updating distf1b5595- Fix: Avoid reporting abort errors on duplicates of same request in451a3f8- Fix: Remove errors for missing query toIDBObjectStore'sgetAllandgetAllKeysfa5dc5e- npm: Bump version to 3.0.0-rc.1050986b4- Refactoring: Make done flag (__readyState) reflect new spec PR Set request result/done flag appropriately in open/delete w3c/IndexedDB#20227f3d54- Refactoring: Avoid redundant versionchange (upgrade) checks inIDBObjectStorec533e21npm: Bump version to 3.0.0-rc.9d00f4e3- Optimization: No-op the harmlessshimIndexedDBset-up properties and methods with a warning30c875d- Docs (README): Add note on caveats of index usagebb222a2- Bump version to 3.0.0-rc.846eb332- Enhancement: AdduseSQLiteIndexesoption to add (and drop) SQLitedbf1b2f- Docs (README): Ensure polyfill added to Unicode example alsofa96ad7- Refactoring (distribution): Avoid baking inbabel-polyfilland make as a regular dependency (so quickly available to browsers)d7fc286- Demo (index.html): Add reference to testing against the latest W3C testsc9761c1- Docs (index.html): WebSql->WebSQLThere are 250 commits in total. See the full diff.