35d7d5f762
Bugfix Issue #1705 (MAUI: 184): Allow null handling for BaseConverterOneWay<TFrom, TTo> ( #1733 )
...
* Fix typo ArgumenException for unit tests
* Add AllowsNullOrDefault handling for BaseConverterOneWay
Fix summary xml doc for ConvertBack of BaseConverterOneWay
* Add BaseConverterOneWay_Tests for new AllowsNullOrDefault
* Implement recommended changes
- Rename test converter to MockConverterOneWay
- Change ArgumentException to ArgumentNullException in BaseConverterOneWay<TFrom, TTo> when disallowing nulls
- Simplify unit test data generation and execution
* Update null check in BaseConverterOneWay<TFrom, TTo>
* Implement recommended changes
- Change check order back to original in BaseConverterOneWay<TFrom, TTo>
- Fix missing first paramName argument for ArgumentNullException in BaseConverterOneWay<TFrom, TTo>
- Refactor BaseConverterOneWay_Tests
* Rename property AllowsNullOrDefault to AllowsNull of BaseConverterOneWay<TFrom, TTo>
* Update IsNullOrEmptyConverter to inherit from BaseConverterOneWay<TFrom, TTo>
* Migrated more converters to base
* Revert compare converter changes
* Fixed unit tests and code review tidy up
* Switch to separate nullable converter base class
* Add null support to BaseConverter
NullableBaseConverter now completes symmetry with NullableBaseConverterOneWay.
Migrate converters to use NullableBaseConverter where possible.
Migrate tests to new approach.
* Remove Null-Forgiving Operator
* Rename converters to start with Base
* Code review improvement
* Add global.json
Ensures .NET 6.0 is the minimum version in use
* `dotnet format`
* Move global.json to root folder
* `dotnet format`
Co-authored-by: Pascal Ried <p.ried@comventure.de>
Co-authored-by: Shaun Lawrence <shaunrlawrence@gmail.com>
Co-authored-by: Pedro Jesus <pedrojesus.cefet@gmail.com>
Co-authored-by: Brandon Minnick <13558917+brminnick@users.noreply.github.com>
2021-12-03 14:37:41 +00:00
d74ab1d633
Enable Nullable ( #1009 )
...
* Enable Nullable on Unit Tests (#1008 )
* Enable Nullability on Xamarin.CommunityToolkit.Markup (#1013 )
* Enable Nullable on Unit Tests
* Enable Nullable on Xamarin.CommunityToolkit.Markup
* Enable Nullability on Xamarin.CommunityToolkit.Sample (#1014 )
* Enable Nullable on Unit Tests
* Enable Nullable on Xamarin.CommunityToolkit.Markup
* Enable Nullable on Xamarin.CommunityToolkit.Sample
* Enable Nullability for Android, GTK, iOS, Tizen, UWP & WPF Sample Projects (#1015 )
* Enable Nullable on Unit Tests
* Enable Nullable on Xamarin.CommunityToolkit.Markup
* Enable Nullable on Xamarin.CommunityToolkit.Sample
* Enable Nullable on Android, GTK, iOS and Tizen Samples
* Enable Nullable for UWP & WPF Sample Projects
* Enable Nullability on Xamarin.CommunityToolkit (#1016 )
* Enable Nullable on Unit Tests
* Enable Nullable on Xamarin.CommunityToolkit.Markup
* Enable Nullable on Xamarin.CommunityToolkit.Sample
* Enable Nullable on Android, GTK, iOS and Tizen Samples
* Enable Nullable for UWP & WPF Sample Projects
* Add Nullability
* Enable Nullable on XamarinCommunityToolkit (#1023 )
* Enable Nullable on Unit Tests
* Enable Nullable on Xamarin.CommunityToolkit.Markup
* Enable Nullable on Xamarin.CommunityToolkit.Sample
* Enable Nullable on Android, GTK, iOS and Tizen Samples
* Enable Nullable for UWP & WPF Sample Projects
* Add Nullability
* Resolve Possible Null References
* Removed Possible Null References
* Update AppResources.Designer.cs
* Handle Nullability
* Updated Nullabiltiy
* Update Converters & Unit Tests
* Resolve MediaSource Unit Tests
* Fix Unit Tests (#1036 )
* Enable Nullable on Unit Tests
* Enable Nullable on Xamarin.CommunityToolkit.Markup
* Enable Nullable on Xamarin.CommunityToolkit.Sample
* Enable Nullable on Android, GTK, iOS and Tizen Samples
* Enable Nullable for UWP & WPF Sample Projects
* Add Nullability
* Resolve Possible Null References
* Removed Possible Null References
* Update AppResources.Designer.cs
* Handle Nullability
* Updated Nullabiltiy
* Update Converters & Unit Tests
* Resolve MediaSource Unit Tests
* Fix VariableMultiValueConverter
* Fixed ImpliedOrderGridBehavior
* Update NumericValidationBehavior.shared.cs
* Resolve Nullable in SideMenuView
* Move <Nullable>enable</Nullable> to Directory.Build.props
* Update Xamarin.CommunityToolkit.Sample.csproj
* Revert Designer.cs
* Update Xamarin.CommunityToolkit.Sample.csproj
* Update ItemSelectedEventArgsConverter_Tests.cs
* Update SearchViewModel.cs
* Update ItemTappedEventArgsConverter_Tests.cs
* Update Xamarin.CommunityToolkit.UnitTests.csproj
* Add Nullability
* Resolve Compiler Warnings
* Ignore Closing square brackets should be spaced correctly
With Nullable enabled, `byte[]?` is now valid, however SA1011 was still generating a warning
* Update src/CommunityToolkit/Xamarin.CommunityToolkit/Behaviors/ImpliedOrderGridBehavior.shared.cs
Co-authored-by: Pedro Jesus <pedrojesus.cefet@gmail.com>
* Update CameraFragment.android.cs
* Update CameraFragment.android.cs
* Update ImpliedOrderGridBehavior.shared.cs
* Update MaskedBehavior.shared.cs
* Update PopupRenderer.uwp.cs
* Use .NET 5.0
* Update azure-pipelines.yml
* Update azure-pipelines.yml
* Update azure-pipelines.yml
* Add UWP to Release Build
* Update Nullability
* Update Nullablity
* Update TabView.shared.cs
* Update Nullability
* Revert "Update Nullability"
This reverts commit e391b9c6540842280e3677226bfd184eb36f4126e41a477dc4#965 )
* Add Non-WPF Support to .NET Core 3.1
* Update comments
* Merge .NET Standard and WPF Functionality
* Fix Null Reference
* Update ICommand_AsyncValueCommand_Tests.cs
* Add volatile keyword
* Update AsyncValueCommand_Tests.cs
* Remove Timeouts
* Fix Event Unsubscription
* Add .ConfigureAwait(false);
* Run dotnet test serially
* Use SemaphoreSlim to prevent Race Conditions
Co-authored-by: Pedro Jesus <pedrojesus.cefet@gmail.com>
Co-authored-by: Maksym Koshovyi <maximkoshevoi61@gmail.com>
2021-03-09 08:24:05 -08:00
Countryen
Brandon Minnick
Pedro Jesus
Gerald Versluis