A RAML parser based on PyYAML written in CoffeScript and available for use as NodeJs module or in-browser.
some other things i've been thinking on to is strongly typed http requests and responses modelled from raml in node (e.g. using typescript definitions)
this means that for each endpoint I’d have a ready-to-go request object or… thing that i can just execute with parameters specified
abao is all about querying a raml endpoint and then checking the response against the schema, but out of the box you can’t test the same endpoint more than once
I was starting to build a sort of ‘Endpoint’ class or somethign that I would pass the raml definition to at construction and it would have some sort of endpoint.query({ param1: x, param2: y }) method.
You could then take the response of the query and do endpoint.validate(response) or something and it’d give you a schema validation
or validate the requesting body
I think the client generation project that Blake was, and still is, working on would help here. I'll let Blake and you sort it out. There is a branch with 1.0 support that would help you. @blakeembrey guess the raml-generator project would be base for what @ProLoser wants to do right?
i want to generate a request
but i would imagine that there might be some degree of shared logic
I’m really hoping somebody can point me in the right direction
is RAML 1.0 still too early to be using in production?
i don't know if any of us can say that definitively
but you'll definitely run into trouble parsing it and using it currently
not everything is up to date and the spec is not yet final
gotcha
ok so, lets assume I’m going with
RAML 0.8 - And I’d like to have a way to test my api.raml on my client side UI via javascript
@blakeembrey in my client-side UI code, or to simplify… lets just say on my local dev environment I have just a
index.html:[…]
<body>
<script type=“text/javascript>
jQuery.ajax( {
url: ‘http://localhost/api/helloWorld',
type: ‘GET',
success: function( response ) {
// response
}
} );
</script>
</body>
</html>
@blakeembrey and my raml…
#%RAML 0.8
title: my api
version: v1
baseUri: http://api.samplehost.com
/helloWorld:
get:
responses:
200:
body:
application/json:
example: |
{
"message" : "Hello World"
}
bear with me… perhaps something syntactically incorrect in these … but just for the sake of argument lets assume they’re correct
yes yes and yes lol
so do you need these synchronised somehow?
raml is just the description language between them
do you want to mock the backend or something to test?
basically, I need a local server - something like this: https://github.com/isaacloud/local-api (although, this doesnt quite satisfy my needs)
yes i need to mock the backend
I guess I’m just hoping perhaps somebody knew of a solution thats even better, or any advice at all for that matter
seems quite good, i'd built https://github.com/mulesoft-labs/osprey-mock-service in the past but it's not quite as complete on the mocking front
I dont want the value of the file but the file name "....schemas.json"