redhat-developer/vscode-yaml

validate doesn't flag unknown fields

Open

#333 opened on Jul 28, 2020

View on GitHub
 (2 comments) (0 reactions) (0 assignees)TypeScript (259 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (820 stars)
PR merge metrics
 (PR metrics pending)

Description

I've created a schema, and while the plugin will suggest to me fields, and flag when I add the wrong types for know fields,

it does NOT flag if I add random new fields / wrongly named fields to the doc.

Is there a strict setting or something similar?

currently it's very easy to name a field like numbr instead of number and get no warning

also the actual suggestion ctrl-space seems to not suggest a lot of stuff.

is there a way to run a "validate" command to flag all the problems? I do see some issues come up in the Problems panel while editing, but only while I'm in the middle of typing and the data is in incomplete / editing mode. As soon as it's finished all my bugs/mitsakes get ignored.

Contributor guide

Research direction
Investigate the YAML validation logic in the extension to see how unknown fields are handled. Check if there is a configuration option like 'strict' or 'additionalProperties' that can be enabled to flag unknown fields. Look at the schema validation code and tests.
Tech stack
typescript
Domain
developer experiencetooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
VS Code extension developmentJSON Schema
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70