textileio / js-threaddb

This project has been moved to https://github.com/textileio/js-textile
https://github.com/textileio/js-textile
MIT License
14 stars 1 forks source link

chore(deps): Bump dexie from 3.0.2 to 3.0.3 #61

Open dependabot[bot] opened 3 years ago

dependabot[bot] commented 3 years ago

Bumps dexie from 3.0.2 to 3.0.3.

Release notes

Sourced from dexie's releases.

Dexie v3.0.3

Changes since 3.0.2

This release contains fixes that improves error resilience, typing correctness and bug fixes for some edge cases.

Typing fixes

  • Fix Table.bulkGet return typing to include undefined #1098
  • Allow readonly arrays for bulk put & get methods #1106
  • Use error keys insted of values for typescript #1115

NOTE: Conditional types is now being used in dist/dexie.d.ts. If you are on an ancient typescript version (below 2.8) you will need to update typescript in your dev deps!

Improvements

  • Verify schema on open #1108
  • Repro + resolve issue #1112: typescript declaration of id makes autoInc fail #1119
  • #1136: Allow declaration-only tables for TS users

Bugfixes

  • Allow middleware hooks to return objects that contained field names that contain dotted strings #1130
  • Resolve #1127 #1131
  • #1146: Resolve #1145 Regression: SchemaError during version upgrade
  • Bugfix of #1154 (PR #1155): WhereClause.equals(undefined) should fail, but it does not fail in dexie 3.0.0-3.0.2. It behaved correctly in dexie 2.x so it's a regression. It is important that libraries fail on invalid arguments so that subtle application bugs are nailed down more easily.

Addons

  • Issue 1048 Typings of addons for Dexie 3.0 #1117 The addons are released with the "next" tag on npm, so please test them and help me verify that #1048 is solved:
    npm i dexie-observable@3.0.0-beta.9
    npm i dexie-syncable@3.0.0-beta.9
    
  • #1138: Dexie.Observable: startObserving function: remove read-only query in order to avoid TransactionInactiveError
  • Bugfix of #1148 (PR #1149).

v3.0.3-rc.4

Bugfix of #1154 (PR #1155): WhereClause.equals(undefined) should fail, but it does not fail in dexie 3.0.0-3.0.2. It behaved correctly in dexie 2.x so it's a regression. It is important that libraries fail on invalid arguments so that subtle application bugs are nailed down more easily.

Dexie v3.0.3-rc.3

Bugfix of #1148 (PR #1149).

Dexie v3.0.3-rc.2

Another Release Candidate

Please help me test this release candidate that contains various fixes and improvements. It's released with the "next" tag on npm instead of "latest". Will release it with the "latest" tag after a week unless someone finds backward compability issues or regression bugs.

npm i dexie@3.0.3-rc.2

New fixes since 3.0.3-rc.1

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)