-
Notifications
You must be signed in to change notification settings - Fork 280
Add support for RAML 1.0 specification #837
Comments
It could! Basically, adding support for a new API description format goes like this... Dredd consumes API Elements. It uses Fury.js to turn any API description format (currently API Blueprint and Swagger 2.0) into API Elements. To produce API Elements for various formats, Fury.js uses adapters. So the first and the most important step to add support for RAML to Dredd would be to create an adapter for Fury, similar to the one for Swagger. The Fury.js maintainers (@apiaryio/adt) would definitely give a hand and advice to anyone who starts with this. Note: A scheme of Dredd's parsing stack is in #820, I'd be happy to re-draw it and add it to docs if there's someone who actually needs it. |
Having support for RAML 1.0 in Dredd would be seriously cool. Guess the difficulty might be to write a parser for a RAML document into API Elements. |
uh for giggles, what would be some prerequisite knowledge needed to help out here? |
@ChrisDillinger I'd say you need a knowledge of RAML, API Elements, and JavaScript. |
Does this announcement change something? Does it still make sense to support RAML in Dredd? |
Close as outdated |
Could Dredd support raml specification?
There is nice node.js parser for the 1.0 RAML
The text was updated successfully, but these errors were encountered: