Skip to content

Investigate kv-storage standard proposal #86

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
cyrilletuzi opened this issue Mar 1, 2019 · 1 comment
Closed

Investigate kv-storage standard proposal #86

cyrilletuzi opened this issue Mar 1, 2019 · 1 comment
Assignees
@cyrilletuzi
Labels
enhancement

Comments

@cyrilletuzi
Copy link
Owner

There is a standard proposal called kv-storage (for key-value storage), which goal is exactly the same as the main goal of this lib: having a simple key-value storage like localStorage, but asynchronous to be performant via indexedDB.

Investigation is needed to prepare to this new API, to be sure the lib API is consistent.
@cyrilletuzi cyrilletuzi self-assigned this Mar 1, 2019
@cyrilletuzi cyrilletuzi added this to the v8.0 milestone Mar 21, 2019
@cyrilletuzi
Copy link
Owner Author

Done in #100

.values() and .entries() have not been implemented as:

  • I don't see a use case,
  • would be bad for performance,
  • could be easily implemented by user via keys()

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cyrilletuzi cyrilletuzi

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cyrilletuzi