AXAML IntelliSense not working correctly/inconsistent

[DeltaDesigns]

Describe the bug

I'm a new Avalonia user so forgive me for anything I may have missed/messed up.
Intellisense doesn't seem to be triggering automatically in axaml files when the parent element is a Grid, only certain members belong to Grid are shown.
Using 'Edit->IntelliSense->List Members' is a workaround but is pretty inconvenient

To Reproduce

See screenshots

AvaloniaVS plugin version

11.11.1.3

Avalonia version

11.3.11

Visual Studio version

17.14.25

Relevant log output

N/A

Additional context

TextBlock with a Grid parent:

TextBlock with a Border parent:

[mrlacey]

Yep, that's a bug.

It appears that the list of completions within a type aren't being shown correctly, but the attached properties for the Grid are always shown.

After completing the name of the element or an attribute pressing a space should prompt the display of all completions options.
It's not.

Apart from when the container is something that alters its contents with attached properties

Invoking the completions (ctrl + space as a shortcut) does prompt the full list to be shown and is filtered if anything is already typed.

[RobG66]

Yep, that's a bug.

It appears that the list of completions within a type aren't being shown correctly, but the attached properties for the Grid are always shown.

After completing the name of the element or an attribute pressing a space should prompt the display of all completions options. It's not.

It's an absolutely huge PITA bug! And it's worse than just the completions not showing:

• The completion options being shown can be valid for a parent control, but not the control you are editing
• Pressing tab to auto complete a blob of code usually omits the closing tag

Rob

[mrlacey]

@RobG66 This:

The completion options being shown can be valid for a parent control, but not the control you are editing

Is a separate issue. Working on a fix now.

---

Can you explain more by what you mean with the following:

Pressing tab to auto complete a blob of code usually omits the closing tag

Can you provide an example?

[RobG66]

@RobG66 This:
Can you explain more by what you mean with the following:

Pressing tab to auto complete a blob of code usually omits the closing tag

Can you provide an example?

• Just make a brand new Avalonia MVVM app.
• Delete the welcome textbox
• Type <Splitview

You can see the code suggestion without a closing tag for the splitview.

Is it supposed to close the entire blob with /SplitView as part of the suggestion?

Rob

[mrlacey]

@RobG66 This:
Can you explain more by what you mean with the following:

Pressing tab to auto complete a blob of code usually omits the closing tag

Can you provide an example?

• Just make a brand new Avalonia MVVM app.
• Delete the welcome textbox
• Type <Splitview

You can see the code suggestion without a closing tag for the splitview.

Is it supposed to close the entire blob with /SplitView as part of the suggestion?

Rob

That grey text is provided by Copilot, not the Avalonia extension.
But yes, it's not great that it doesn't provide valid XAML.

If interested, you can disable (and/or [re]enable) it via the Copilot settings menu.

[mrlacey]

The 18.5.0 release of Visual Studio includes a change to stop the copilot suggestion and intellisense options competing

IntelliSense takes priority over Copilot