Youssef Victor

IIRC, the helper takes TestIdGenerationStrategy or something like that which exists today for backcompat reasons which we may want to break in v4. So might be better to expose the...

Not going to do this breaking change, at least in v4. Instead, we will automatically use the default display name when `GetDisplayName` returns null.

We probably should re-use https://github.com/CommunityToolkit/Labs-Windows/blob/8d49097c09d5e07fa225d0fbf014cc4774c99cfb/components/AppServices/CommunityToolkit.AppServices.SourceGenerators/Extensions/ITypeSymbolExtensions.cs#L22 for the hint name

**All** Roslyn generators are given the same compilation. So there is no concept of order. No generator can see the output of another.

The safest action is to not generate [Bindable], and instead implement an analyzer that warns the user for this case and suggest adding a non-generated partial with [Bindable]. Yes it's...

Alternatively, the bindable generator may be complicated so that it tries to anticipate what the view model generator would be generating and act as if the attribute is seen. This...

> This is not possible: the "bindable" applies to the code generated by the MVUX generator. Even if user adds the [Bindable] himself the code will not be present yet....

> Because even if the user creates a partial VM class it will be empty as content is fully generated by the mvux-gen (including properties), so the bin-gen won't be...

@DevTKSS The AI-generated content you got doesn't look correct to me. No generator can access syntax/semantics that is generated by another generator. That is an unfortunate limitation, but that is...

@Evangelink Is this actionable?