Support for validation

[char0n]

Currently the POC parser doesn't validate the data. The question here is should it? As we stipulated before this POC started, the aim of ApiDOM is to use existing ADD parsers/validators like: https://www.npmjs.com/package/swagger-parser

[char0n]

Note: future validation errors should be embed directly into ApiDOM, and not to top level collection of errors.

[char0n]

@frantuma this needs to be discussed further and strategy for validation needs to be agreed upon before this ticket can be estimated.

[frantuma]

Adding @frantuma to assignees, as working on it, Validation for POC based on json schema and few other defined rules, Design should allow for plugin of custom validation providers (for custom linting, etc)

[char0n]

@frantuma just note here: ApiDOM was designed by having validation in mind. It was discussed briefly, but I'll summarize it here:

I was expecting to use Visitor pattern for validation either on grammar specific JSON CST/AST or ApiDOM itself. Having validation coupled with JSON CST/AST IMHO makes most sense as it doens't make sense to validate already created ApiDOM structures

Validation is an opt-in mechanism that optionally plugs in after the tree-sitter CST is transform to our AST but before the ApiDOM is produced. Using JSON Schema for validation requires the original source code (OpenAPi spec in string) to be available and additional parsing needs to be involved to parse the document and run it via JSON Spec validation. Using custom validation by visiting makes use of already available AST.

Does standard javascript JSON Schema implementations support YAML out of the box?