-
Notifications
You must be signed in to change notification settings - Fork 327
Closed
Labels
Description
Describe the bug
The range of key ordering errors is weird. Sometimes it starts before the out of order key, sometimes it ends after the out of order key.
Here is an example YAML that shows this behaviour:
one:
child: moo
two:
mild: meh
child: moo
three:
child: mooExpected Behavior
There are two errors, one that covers two: and one that covers mild:.
Current Behavior
There are two errors, one that starts at two: and continues to the next line for two characters, and one that starts at mild: but continues past the : by one character.
Steps to Reproduce
- Enable key ordering errors, eg.
"yaml.keyOrdering": true, - Make the above YAML
- Observe the wonky error ranges
Environment
- Windows
- Mac
- Linux
- other (please specify)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Done