redhat-developer / redhat-developer/vscode-yaml
yaml.maxItermsComputed ignored
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 829
- Forks
- 260
- Avg merge
- 5h 43m
- Merged PRs (30d)
- 1
Description
Describe the bug
My yaml file is a hierarchical structure for describing plants: https://wikibotanica.net/static/plant_schema.yaml . When I load it in vscode with the yaml extension, I get the warning:
For performance reasons, document symbols have been limited to 5000 items. Use setting 'yaml.maxItermsComputed' to configure the limit.
I duly edit the user and workspace settings to say 20,000 (I've tried various numbers including 1000000 just for fun), but I still get the error. This behaviour is not consistent, the error may not happen for a few openings but it does recur over time.
This is with extension version 1.14 and multiple vscode versions, currently 1.80.1
Expected Behavior
The extension should 'compute' all documents.
Current Behavior
As stated, the error occurs. I'm not sure whether this means the file is partially parsed - yaml syntactic errors are caught throughout the file and I can fully use it in my app. At the minimum it is an annoying message.
Steps to Reproduce
- with the yaml language extension loaded in vscode, open the yaml file
- error occurs
- adjust yaml.maxItermsComputed
- close the yaml file, then close vscode
- restart vscode and open the yaml file
Environment
- Windows
- Mac
- Linux
- other (please specify)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the warning in the VS Code YAML extension with the linked plant_schema.yaml file and the yaml.maxItermsComputed setting. No source file or test is named, so trace how this setting reaches document-symbol computation; done means the configured limit is honored and the warning no longer appears unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100