Skip to content
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

use SQLitePCL.Batteries_V2.Init() instead of the original #338

Merged
merged 3 commits into from
May 20, 2017
Merged

use SQLitePCL.Batteries_V2.Init() instead of the original #338

merged 3 commits into from
May 20, 2017

Conversation

ericsink
Copy link
Contributor

@ericsink ericsink commented Jan 4, 2017

Batteries.Init(). the new one does exactly the same thing, but supports bait-and-switch across bundle types, which eases difficulties that can happen when using multiple libraries that use SQLitePCL.raw.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

bug fix (more or less)

What is the current behavior? (You can also link to an open issue here)

call SQLitePCL.Batteries.Init()

What is the new behavior (if this is a feature change)?

call SQLitePCL.Batteries_V2.Init()

Does this PR introduce a breaking change?

no

Please check if the PR fulfills these requirements

Other information:

…nit(). the new one does exactly the same thing, but supports bait-and-switch across bundle types, which eases difficulties that can happen when using multiple libraries that use SQLitePCL.raw.
@ericsink
Copy link
Contributor Author

ericsink commented Jan 4, 2017

Not sure my commit message follows the guidelines. Feel free to tell me I need to redo this and be more careful.

@ericsink
Copy link
Contributor Author

ericsink commented Jan 4, 2017

Bottom line here is that this change is not urgent, so no need to rush and release a new package on nuget. I'm just trying to steer everybody toward Batteries_V2.Init().

@ghuntley ghuntley added this to the next milestone Jan 16, 2017
Copy link
Member

@ghuntley ghuntley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we also need to bump the version from nuget? Ie upgrade package dependencies.

@ericsink
Copy link
Contributor Author

Updating the package dependencies is not necessary. The nuspec file here indicates it is using my version 1.1.0, which is the minimum needed for Batteries_V2.

If you want to update the dependency to a more recent version, you can, and it should cause no problems, but it should not be necessary for this pull request.

@ghuntley ghuntley self-assigned this Jan 17, 2017
@ghuntley ghuntley merged commit cf13bae into reactiveui:develop May 20, 2017
@lock lock bot locked and limited conversation to collaborators Jun 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants