Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

Fix CoerceValue() method #15031

Closed
wants to merge 1 commit into from
Closed

Fix CoerceValue() method #15031

wants to merge 1 commit into from

Conversation

SuNNjek
Copy link
Contributor

@SuNNjek SuNNjek commented Jan 7, 2022

Description of Change

Fixes CoerceValue() so it actually sets the value of the bindable object.

Issues Resolved

API Changes

None

Platforms Affected

  • Core/XAML (all platforms)

Behavioral/Visual Changes

CoerceValue() updates the value of the object now.

Before/After Screenshots

Not applicable

Testing Procedure

See reproduction and expected/actual behavior in #15024

PR Checklist

  • Targets the correct branch
  • Tests are passing (or failures are unrelated)

@nmiller-lci
Copy link

@StephaneDelcroix @jsuarezruiz
Are there any concerns with this being merged? Just came across this issue.

@jfversluis
Copy link
Member

Now that we're so close to the sunsetting of Xamarin.Forms unfortunately we won't be able to take this in anymore, we're really sorry about that. Nevertheless, thank you so much for your time and effort that you have put into this PR.

Please have a look at the evolution of Xamarin.Forms, .NET MAUI. A lot of development has been going on there. Hopefully this issue was already fixed in that codebase. If not, feel free to port this over to there.

Again, thank you so much for being a contributor and Xamarin.Forms user!

@jfversluis jfversluis closed this Apr 25, 2024
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.

[Bug] CoerceValue() does nothing
4 participants