Repository navigation
feat: bumped sqlite-wasm to v3.54.1 - #176
Merged
Merged
Conversation
Collaborator
Excellent question. Let's leave that one documented, as it gives users a way to opt out of a difficult and decisive design decision which has long been a default. |
Contributor
Author
|
Awesome, thank you! In this case, @tomayac, this one is all yours! 😄 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
sqlite 3.54.1 build. I also expanded the types with some properties we missed in 3.53 version.
@sgbeal, do you want
preserveOnInitFailureto be documented, or should I omit it (as we do withforceReinitIfPreviouslyFailed)?