Trim off <|file_separator|> from autocomplete completion for Google Models

[hayden-cardwell]

Validations

• I believe this is a way to improve. I'll try to join the Continue Discord for questions
• I'm not able to find an open issue that requests the same enhancement

Problem

When using Google models for FIM/AutoComplete, they will sometimes return <|file_separator|> at the end of their completion. This results in the end-users inability to use the autocomplete completion without removing <|file_separator|> manually for each suggestion.

Solution

Add the following bit of code to the postprocessCompletion function within core/autocomplete/postprocessing/index.ts

if (
    (llm.model.includes("gemini") || llm.model.includes("gemma")) &&
    completion.endsWith("<|file_separator|>")
  ) {
    // "<|file_separator|>" is 18 characters long
    completion = completion.slice(0, -18);
  }

I would like to submit the PR to have this merged, but I'm attempting to follow the contribution guide by creating an issue first. Please let me know how to proceed.

[sestinj]

@hayden-cardwell Appreciate you making the issue first! This would definitely be a great contribution. We already have some utilities in the autocomplete folder for stopping at certain keywords, so you might be able to just add this to one of the arrays in streamTransforms.ts

[hayden-cardwell]

Hi @sestinj,

I attempted to make modifications in:
core/autocomplete/filtering/streamTransforms/lineStream.ts
Specifically by modifying the "LINES_TO_STOP_AT" constant, but that modification only resulted in the completions failing to generate.
As such, I've went ahead and made the above mentioned pull request as that's what I was able to get working.

Thank you!