A cross-browser/platform indexeddb-like client library
Перейти к файлу
George Guskov 6b70241f7f
Merge pull request #62 from bhargeymehta/bhargeymehta/concat-to-push
Improve InMemoryProvider getRange function from O(N^2) to O(N)
2024-09-09 11:40:37 -07:00
.github/workflows Resolved conflicts after rebase - Cleanups to publish to npm (#22) 2024-08-19 16:58:20 -06:00
.vscode
src prettier 2024-09-09 22:43:29 +05:30
.eslintrc.js
.gitignore
.npmignore
.npmrc
.prettierignore
.prettierrc.json
.yarnclean
CODE_OF_CONDUCT.md
CONTRIBUTING.md
LICENSE
README.md Update readme about rebase 2024-08-23 16:18:26 -06:00
SECURITY.md
index.ts add live configs 2024-09-06 20:27:18 +05:30
karma.browser.conf.js
karma.sharedworker.conf.js
karma.webworker.conf.js
package.json add live configs 2024-09-06 20:27:18 +05:30
tsconfig.json
webpack.config.js
yarn.lock

README.md

ObjectStoreProvider Build Status

We developed ObjectStoreProvider after needing a simplified interface toobject storage/retrieval that worked not only across all browsers. We also have built a fully in-memory database provider that has no persistence but supports fully transactional semantics, for a fallback in situations where you don't want persistence (ephemeral logins, etc.)

Differences to NoSqlProvider

This project has some notable differences to NoSqlProvider, and these differences are why it is a separate repo

  1. Support for removeRange apis.
  2. Support for getMultiple on any index.
  3. Unlike in the case of ObjectStoreProvider, the inMemoryProvider is actually mutable. This was mainly done as we enforce immutability using typescript DeepReadonly types. Consumers should be aware of this while consuming the library. In the near future we will change to interfaces throughout the project to return readonly types. It is highly recommended that consumers add lint rules that prevent casting to , or operations like Object.assign() which will break the immutability.
  4. Targets ES6, and higher ES versions for better performance
  5. It uses red-black tree based indices for better performance of the inMemory provider

The rest of these changes in the library have been pushed upstream to ObjectStoreProvider as well. However, points 3, 4 & 5 are irreconcilable as it needs to be enforced across all consumers of ObjectStoreProvider. Hence this repo has been made separately.

Examples

None available, we will add some soon!.

Providers/Platforms/Support

Browsers: Firefox, Safari, Edge, Chrome. Execution Contexts: WebWorkers, SharedWorkers, ServiceWorkers, Browser context.

Desktop Frameworks: WebView2, Electron

Other support: NodeJS

Usage

Coming soon.

Compiling

Source

yarn install
yarn build

Tests

yarn install
yarn ci-test

Testing

If a test fails and you need to run the individual tests, see which test command failed from the above run .i.e karma.sharedworker.conf.js, karma.webworker.conf.js, karma.browser.conf.js Once identified, simply run the following

yarn install
yarn build
yarn test:debug:<target>

Where <target> is either webworker, sharedworker or browser. Look through package.json for more details. The default runner will launch both firefox + chrome in debug mode.

To iterate over tests, instead of the yarn build command mentioned above, run yarn watch instead.

Contributing

Please read the Contributing guide.

NOTE: Commit history in master branch has been modifed (to fix a security issue), so if you have an open PR -or- forked and created a branch, please rebase it with latest master.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsofts Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-partys policies.