Failure to fill out this information will result in this issue being closed.
If you are creating an issue for a BUG please fill out this information. If you are asking a question or requesting a feature you can delete the sections below.
If you post a full stack trace in a bug it will be closed, please post it to http://gist.github.com and then post the link here.
Bug Information
Version Number of Plugin:1.5.0
Device Tested On:
Simulator Tested On: Android Api 31
Version of VS:17.0.5
Version of Xamarin: 5.0
Steps to reproduce the Behavior
Create a Validtable Property to List.
public Validatable<string> Value { get; set; }
Subscribe to the Property's On change event.
Value.ValueChanged += Value_ValueChanged;
Expected Behaviour
When the value is changed, the ValueChanged event should be called once. However it is triggering twice.
Actual Behavior
The event is trigger twice.
Code snippet
Quick look leads me to believe the cause is here:
Value's Setter fires the event and calls FormattedValue's Setter.
FormattedValues's Setter also triggers the same event.
So the fix could be for the Value's Setter to update the FormattedValue's backing field or create another event for
FormattedValueChanged
Failure to fill out this information will result in this issue being closed.
If you are creating an issue for a BUG please fill out this information. If you are asking a question or requesting a feature you can delete the sections below.
If you post a full stack trace in a bug it will be closed, please post it to http://gist.github.com and then post the link here.
Bug Information
Version Number of Plugin:1.5.0 Device Tested On: Simulator Tested On: Android Api 31 Version of VS:17.0.5 Version of Xamarin: 5.0
Steps to reproduce the Behavior
public Validatable<string> Value { get; set; }
Value.ValueChanged += Value_ValueChanged;
Expected Behaviour
When the value is changed, the ValueChanged event should be called once. However it is triggering twice.
Actual Behavior
The event is trigger twice.
Code snippet
Quick look leads me to believe the cause is here:
So the fix could be for the Value's Setter to update the FormattedValue's backing field or create another event for FormattedValueChanged