The completions in the front matter is influenced by the space after the `:`

[TylerLeonhardt]

Screen.Recording.2025-11-25.at.1.16.55.PM.mov

this is really bad in the agents completions:

Screen.Recording.2025-11-25.at.1.19.04.PM.mov

This space prefix should not be counted in the completion

I have noticed this really across the board for all front matter properties so it might need a generic fix.

[aeschli]

It's the completion widget that refilters the list in a way I also don't understand.

[jrieken]

It's the completion widget that refilters the list in a way I also don't understand.

It's all defined by the range and filterText the corresponding completion gives.

What happens here is that (space) is a character that appears in the suggestion's label/filterText and when typing that we rerank the list by match quality - words where space appears at "better/stronger" position rank higher.

[aeschli]

I tried adding filter text, different ranges, marking the list as incomplete (so I'm getting called on every character, but I don't, space sems to be special).
I don't seem to be able to influence the filtering behavior.
That said, typing space is like typing some character and that filters down the list. So I don't think one can expect that the list stays the same. But yes, it filters in a very mysterious way.

No changes planed.

[TylerLeonhardt]

This was a big problem for me because what I was seeing is that sometimes I would accept a completion at the front matter name level, like:

mod|

Which went to

model: 

With a space

But the next completions was already influenced by the space and would show only a subset of the models.

I really think we should do something about this, the experience left me wondering if completions were reliable at all.

[jrieken]

But yes, it filters in a very mysterious way.

Well, typing space will filter those suggestions that don't have space in them. An easy fix would be to have a trailing space at the end of each filterText-property

[TylerLeonhardt]

optimistically reopening since this really pains me (and also pained @sbatten) and @jrieken gives hints that this might be painless to fix.