NRE if use in couple with code generated property

[Alex-Dobrynin]

I'm using this lib over the app and noticed if I do complex binding to the code generated property of CommunityToolkit.Mvvm package ObservablePropertyAttribute, and the property was not set, then I get null reference exception

Example

[ObservableProperty] private UserObservableModel _profile;

and do this in xaml

<Image Source="{x:Bind Profile.ImageUrl, TargetNullValue=images:Images.ImagePlaceholder}" />

F.e. if I have only string property to the image this works ok

[ObservableProperty] private string _imageUrl;

and do this in xaml

<Image Source="{x:Bind ImageUrl, TargetNullValue=images:Images.ImagePlaceholder}" />

Default {Binding Profile.ImageUrl, TargetNullValue=images:Images.ImagePlaceholder} works perfect

[levitali]

You can declare the _profile variable as nullable.

[ObservableProperty] private UserObservableModel? _profile;

Then the x:Bind code generator will generate code checking whether the property is null.

I'm consindering turning off checking whether a reference type is nullable or not, and generate code as it's always nullable.

[Alex-Dobrynin]

@levitali unfortunately I'm not using nullable notations in code for already nullable types (reference types), and disabled it in project settings

[levitali]

I've uploaded a new version. Now nullability of the generated code is dependent on project settings.

[Alex-Dobrynin]

Thx, will check

[Alex-Dobrynin]

In version 1.0.17.5 this bug has returned

also in version 1.0.17.4 getting NRE for nested types which marked as [ObservableProperty]
for example I have

public partial class User : ObservableObject
{
    [ObservableProperty]
    private string _name;
}

and in my viewmodel i have this

[ObservableProperty]
private User _user;

[levitali]

The fix made in 1.0.17.4 caused some troubles in my code, with nullables enabled.

I now published new version 1.0.17.6. It woks well in my projects, as well as it should work in projects with nullables disabled.