(housekeeping) Upgraded Xamarin.Forms to v3.4 #1942
Merged
Conversation
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
Codecov Report
@@ Coverage Diff @@
## master #1942 +/- ##
=======================================
Coverage 67.39% 67.39%
=======================================
Files 99 99
Lines 4815 4815
Branches 465 465
=======================================
Hits 3245 3245
Misses 1443 1443
Partials 127 127Continue to review full report at Codecov.
|
worldbeater
previously approved these changes
Feb 8, 2019
glennawatson
requested changes
Feb 8, 2019
- Cleaned up modifier sorts
glennawatson
approved these changes
Feb 8, 2019
|
I attempted to change the Xamarin version in the Platform to 3.4.*, seems that depends on a full semantic version to resolve correctly. |
glennawatson
pushed a commit
that referenced
this pull request
Mar 23, 2019
* (housekeeping) Upgraded Xamarin.Forms to v3.4
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Upgrade Xamarin.Forms to version 3.4
What is the current behavior? (You can also link to an open issue here)
Xamarin.Forms targets version 3.3
What is the new behavior (if this is a feature change)?
Xamarin.Forms targets version 3.4
What might this PR break?
Xamarin.Forms based controls
Please check if the PR fulfills these requirements