chore: update indexed_db_futures #5347
Merged
Conversation
This file contains 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
jstuczyn
force-pushed
the
chore/indexed-db-futures-update
branch
from
fca7117 to
7c46410
Compare
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
jstuczyn
force-pushed
the
chore/indexed-db-futures-update
branch
from
b295054 to
e50f152
Compare
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.
updates the
indexed_db_futuresdependency to stop relying on the fork.there's been a lot of changes in the API so before it could be merged, I'd need to first create a dummy JS project to double check the behaviour still works, in particular
get_all_keyssince now we're returningVec<JsValue>rather thanjs_sys::Arrayand I have no idea whether JS itself won't freak out because of it (since the list allocation would be in rust instead of js)This change is