Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

RAML 0.8 automated validation #4

Open
alvassin opened this issue May 1, 2016 · 1 comment
Open

RAML 0.8 automated validation #4

alvassin opened this issue May 1, 2016 · 1 comment

Comments

@alvassin
Copy link

alvassin commented May 1, 2016

I want to perform automated validation of following things on git pre-commit hook:

  • RAML 0.8 syntax
  • json-schemas (with $refs)
  • examples (from my experience 99% of mistakes or typos are here, must have)

As i see, this module is not intended to perform this (i even can't see raml-js-parser in dependencies and i can't get how to perform deep validation without it). Perhaps you can advice a best way to implement such validation?

In fact, raml-js-parser itself is able to parse RAML 0.8 and dereference all schemas using key dereferenceSchemas=true. So, perhaps it would be enough to see if RAML file with dereferenced is just being parsed successfully.

Also, there is module tv4 that can validate json against given json-schema. They can be used together to perform automated tests. What do you think?

P.S. I've created in a separate thread, because this issue is about version 1.0.

@dmartinezg
Copy link

Hi @alvassin, this module actually has a far-reaching name for what it does ;), it simply validates named-parameters (like headers, URI params, etc)

It is used from other modules, like https://github.com/mulesoft/osprey , to support full API support, validations, etc. You are right that it does not take an actual RAML file, it takes its parsed output, and a

The right move for this project would be to be renamed, but too many things would break.

I would not be opposed of adding example validations to the RAML parser (I think it is the only missing item from your wish-list)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants