Avalonia

Commit Graph

Author	SHA1	Message	Date
Jeremy Koritzinsky	af186e3529	Move string-based binding paths up to Avalonia.Markup. Make the LINQ Expression paths and raw ExpressionNodes (now public) the primarily supported syntax.	8 years ago
Jeremy Koritzinsky	cf8244b37a	Move current contents of Avalonia.Markup to Avalonia.Base. Move Avalonia.Markup.Xaml.Data/Parser classes to Avalonia.Markup since they're not Xaml-specific. Use pattern-matching switch. Fix bug from cleanup.	8 years ago
ARSolog	8a8a6de9a6	Update ExpressionObserverTests_DataValidation.cs fix Validation_Plugins_Send_Correct_Notifications to non 'en-us' CultureInfo.	8 years ago
Steven Kirk	7baa7dc0dd	Added GC.KeepAlive to tests. Lots of `Avalonia.Markup.UnitTests` were failing intermittently. This is because in release mode, in a method like this: ``` [Fact] public void SetValue_Should_Return_False_For_Missing_Object() { var data = new Class1(); var target = new ExpressionObserver(data, "Next.Bar"); using (target.Subscribe(_ => { })) { Assert.False(target.SetValue("baz")); } } ``` `data` can get GC'ed at any point after creating target. Added `GC.KeepAlive()` calls to prevent this. Fixes #1035 Fixes #1036 Fixes #1037	9 years ago
Steven Kirk	715149b1f5	Improve stream operator error message. When a stream operator is applied to an unsupported type.	9 years ago
Steven Kirk	dd29966f20	Run certain tests in invariant culture. Fixes #718.	10 years ago
Steven Kirk	7cb001801a	Try to improve logged binding errors. - Don't log an error when the target for the root ExpressionNode is null. This is usually because the `DataContext` hasn't been set up yet and it spewed a load of useless error messages. - Add a Description field to `ExpressionObserver` that can be used in the case of e.g. #control bindings to record the whole expression (with the "#control" part) rather than just the part tracked by the `ExpressionObserver`.	10 years ago
Steven Kirk	f59c16bc00	Improve broken binding diagnostic messages.	10 years ago
Steven Kirk	844da05fe8	Revert "Only send BindingNotifications on error." This reverts commit `57e646583f`. For TextBox there can be 2 bindings to Text: one which is the binding to the view model which should have data validation enabled, and another binding to the TextPresenter in the template which should not have data validation enabled, or it will override the view model data validation. For this we need to be able to distinguish between the two and so bindings with data validation enabled need to always send BindingNotifications. Conflicts: src/Avalonia.Base/AvaloniaObject.cs tests/Avalonia.Markup.Xaml.UnitTests/Data/BindingTests_Validation.cs	10 years ago
Steven Kirk	57e646583f	Only send BindingNotifications on error. Assume that a normal value when received by a property with data validation enabled means no error.	10 years ago
Steven Kirk	0c2057e458	Fix failing tests, add other tests. Also use logical parent's DataContext as base for DataContext bindings instead of visual parent's. Was previously in error.	10 years ago
Steven Kirk	2f72295657	Started refactor of ExpressionObserver. Tying to be more "rx", but also will allow us to move forward on BindingNotification changes.	10 years ago
Steven Kirk	4ffae3eb55	Added IndeiBase And use it as base class for test data that implements INotifyDataErrorInfo. Removed IndeiValidatorTests as its been superceeded by IndeiValidationPluginTests.	10 years ago
Steven Kirk	ac427192df	Use NotifyingBase in unit tests. And rename NotifyingBase.SubscriptionCount -> PropertyChangedSubscriptionCount as we also track ErrorsChanged subscription count.	10 years ago
Steven Kirk	4906a472b0	Reimplemented data validation using BindingNotifications.	10 years ago
Steven Kirk	5c33fbc6ee	Reimplemented property validation. As far as it was in `property-validation-grokys` branch. Things were messed up on master so had to merge this manually so may be problems.	10 years ago

2 Commits (af186e35296d396ed74d902c466cda1f4c020741)