Do not throw exceptions in code which can be written in XAML

[VladislavAntonyuk]

It's hard to catch exception in XAML, so in most cases application crashes.

It mostly happens in Converters if some value has invalid type.

So I propose to return default value instead.

In 99% (It's just my opinion) it won't break existing code.

If you assume it's a breaking change we can create a settings flag "ThrowException" which is True by default.

[bijington]

To provide some follow up here, issue #540 was raised highlighting this issue

#540

We see this because we actively support NRT but I think we are coming to realise that not all devs using the toolkit are.

I would like to propose that we enhance the UseMauiCommunityToolkit method to allow for the configuring of options like this:

Sample options class definition

public class MauiCommunityToolkitOptions
{
    public bool EnableNullReferenceTypeSupport { get; set; } = true;
}

Sample usage scenario

builder
    .UseMauiApp<App>()
    .UseMauiCommunityToolkit(options =>
    {
        options.EnableNullReferenceTypeSupport = false;
    });

With the aim that the existing method will behave as it currently does if no options are defined.

[CliffAgius]

Closed as answered