Feat: support maxStopWords model config option in yaml #5675
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I described the problem in this issue: #5663
Whats changed is that the
maxStopWords
config option that was present in the deprecated JSON but not in the YAML configuration is added to the YAML schema.Checklist
Screenshots
Tests
I tested it using the vscode debug feature, with the config shown in the issue that initially led to the described error. After the changes, the
maxStopWords
config option is correctly working when using YAML config, leading to the same result as if the JSON version of the same config would be used.Summary by mrge
Added support for the maxStopWords model config option in YAML, matching the previous JSON config behavior.