fix: add autocompleteOptions in the .yaml config

[panyamkeerthana]

Description

-This re-enables the deprecated tabAutocompleteOptions support to the YAML configuration schema on the global level and adds experimental parameters to tabAutocompleteOptions schema to enable overriding default values from parameters.ts via config.yaml files. Did this to keep the context limited to the current opened file.

• Re-integrated tabAutocompleteOptions into the global YAML config schema.
• Added .optional() tags to schema properties to allow partial overrides.
• Updated loadYaml.ts to properly transfer YAML values into the final continueConfig.
• Updated unroll.ts to ensure proper propagation of tabAutocompleteOptions during config unroll.

To restrict tab autocomplete context to just the currently opened file, add this configuration to config.yaml:

Example config.yaml

tabAutocompleteOptions:
  useRecentlyEdited: false
  useRecentlyOpened: false
  experimental_includeClipboard: false
  experimental_includeRecentlyVisitedRanges: false
  experimental_includeRecentlyEditedRanges: false
  experimental_includeDiff: false
  experimental_enableStaticContextualization: false

This PR is supposed to resolve #6767

[panyamkeerthana]

Hey @Patrick-Erichsen, here's the PR as discussed!

[Patrick-Erichsen]

The CI errors are here likely related to some recent changes on main looking into it now 👍

[panyamkeerthana]

Haha Thank you! @Patrick-Erichsen

[RomneyDa]

@panyamkeerthana there is already an autocompleteOptions property on the model config. It appears to be undocumented. Were you aware of this, or is it missing specific properties?

[panyamkeerthana]

@RomneyDa Yes, I was aware of this and you're right! It was missing the context restriction properties but so was tabAutocompleteOptions.

I guess, my understanding of it was that context behavior is a user preference that should apply across all models through a single config point. However, I'm open to moving this to a model-level config if you feel that will provide a more modular config design! 😊

[RomneyDa]

Got it! A nice thing about YAML is that you can use YAML templating to easily add the same configuration to all models, in an assistant, which isn't fully the single-point effect but pretty close. You were probably already aware of that as well, I think we would prefer the more modular approach

[panyamkeerthana]

Really good point about YAML templating, appreciate the perspective.😁 I’ll get the changes pushed soon!

[RomneyDa]

@panyamkeerthana could you revert extraneous package lock and completion provider changes?

[RomneyDa]

@panyamkeerthana also add docs for the the non-experimental options?
Could take inspiration from @ferenci84's implementation here #6940

[panyamkeerthana]

@RomneyDa I've added to documentation. Thanks for pointing me to @ferenci84’s implementation, really helpful! 🙌 😊