-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Should OpenDbRequest::set_on_upgrade_needed
take a callback that returns a future?
#30
Labels
Released
This issue's resolution is now available in a published release
Comments
OpenDbRequest
take a callback that returns a future?OpenDbRequest::on_upgrade_needed
take a callback that returns a future?
OpenDbRequest::on_upgrade_needed
take a callback that returns a future?OpenDbRequest::set_on_upgrade_needed
take a callback that returns a future?
Alorel
added a commit
that referenced
this issue
Oct 27, 2024
Alorel
added a commit
that referenced
this issue
Oct 27, 2024
Alorel
added a commit
that referenced
this issue
Oct 27, 2024
Alorel
added a commit
that referenced
this issue
Oct 27, 2024
Alorel
added a commit
that referenced
this issue
Oct 27, 2024
Alorel
added a commit
that referenced
this issue
Oct 27, 2024
Alorel
added a commit
that referenced
this issue
Oct 27, 2024
Alorel
added a commit
that referenced
this issue
Oct 27, 2024
Alorel
added a commit
that referenced
this issue
Oct 27, 2024
Alorel
added a commit
that referenced
this issue
Oct 27, 2024
This issue has been included in v0.6.0 🎉 - Your friendly neighbourhood 🤖 semantic release bot |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the callback we might need to
await
a transaction to make sure everything happens in the correct order.For example porting the example of the "Structuring the database" section of MDN's guide is currently not possible.
They recommend to wait for the
createObjectStore
transaction to be completed before adding data in it. In Rust code that requires turning the transaction into a future.The text was updated successfully, but these errors were encountered: