-
Notifications
You must be signed in to change notification settings - Fork 154
utility crate: Indexed DB #2
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.
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
Comments
It should also fully support Futures, since all the IndexedDB APIs are asynchronous. |
I think approaching with a similar high level semantics, like Dexie in JS, would probably be the key in making it actually usable. Indexed DB is tedious to use as it is, and I'm afraid of even thinking about a Rust-y future chaining for low level request, responses and error handling of IndexedDB. |
I agree that we want to get there, but I am a big fan of creating layers that go from raw |
Absolutely in agreement. Just wanted to clarify on what layers are being set as expectations in the scope of |
See also the discussion happening in #27 about layers of APIs. |
I'm experimenting with a high level indexed db wrapper (futures based) here. Feedback is welcome. 😁 |
Should have a utility crate for working with Indexed DB in a Rust-y, idiomatic way.
The text was updated successfully, but these errors were encountered: