No autocomplete for tokens within interpolated strings (within Ionide/VSCode)

[kojo12228]

When trying an interpolated string, I don't get auto complete while typing out a variable or type name. Even once a valid token is entered, I don't get autocomplete of properties/functions/types etc.

See the GIF below for an example. It's easily reproducible with any interpolated string:

If the issue is new joiner friendly, I'm happy to look into trying to fix it myself (even if it isn't hopefully a weekend soon I'll take a look).

[baronfel]

Super interesting! I can get a completion list when I manually invoke completions inside a { context (via CTRL + Space):

But it looks like { isn't a trigger character to open the completion list, and we also might have something going on with detecting an interpolated string context for completions.

The easiest way to look at this would be to add a new test to the existing completion tests (test\FsAutoComplete.Tests.Lsp\CompletionTests.fs) for this scenario, then debug it.

[github-actions]

🤖 This is an automated response from Repo Assist.

Hi! After investigating this, the root cause is a one-line omission: { is not in FSAC's TriggerCharacters list for completion (Common.fs declares TriggerCharacters = Some([| "."; "'" |])).

LSP clients only send automatic completion requests for characters in that list, which is why Ctrl+Space works (manual invocation) but typing { doesn't trigger auto-complete.

I've submitted a draft PR that adds { to the trigger characters list — if merged, completions will appear automatically when you type { inside an interpolated string (and in record expressions / computation expressions too).

Generated by Repo Assist

To install this workflow, run gh aw add githubnext/agentics/workflows/repo-assist.md@ee50a3b7d1d3eb4a8c409ac9409fd61c9a66b0f5. View source at https://github.com/githubnext/agentics/tree/ee50a3b7d1d3eb4a8c409ac9409fd61c9a66b0f5/workflows/repo-assist.md.