microsoft / microsoft/vscode-textmate
yaml highlighting/textmate recognises some integers as strings (or vice versa?)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 678
- Forks
- 135
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 2
Description
Some integers (or strings?) are treated differently even though they look the same to me.
In each comment I've specified what the scope inspector reports the scope as.
Testcase:
test:
- test: 01 # constant.numeric.integer.yaml
- test: 02 # constant.numeric.integer.yaml
- test: 03 # constant.numeric.integer.yaml
- test: 04 # constant.numeric.integer.yaml
- test: 05 # constant.numeric.integer.yaml
- test: 06 # constant.numeric.integer.yaml
- test: 07 # constant.numeric.integer.yaml
- test: 08 # string.unquoted.plain.out.yaml
- test: 09 # string.unquoted.plain.out.yaml
- test: 10 # constant.numeric.integer.yaml
This is what it ends up looking like for me:
I'd expect them all to be the same; so either they should all be integers or they should all be unquoted strings. Right?
Contributor guide
No contributing guide indexed for this repository
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 loading the YAML testcase from the issue and inspecting the reported scopes for 01–10 with the scope inspector. Trace the YAML grammar entry point that assigns these scopes; done means the values receive the intended consistent classification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, yaml
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100