Feature/expandable schemas

[alvassin]

Added flag dereferenceSchemas, that allows to preprocess json-schemas and provide resolved $refs. Fixes #140

[dmartinezg]

What if you have this RAML:

#%RAML 0.8
/foo:
  post:
    body:
      schema: !include someFastFile.json
schemas: !include someSlowFile.yaml

You should defer all schema reading and processing, until all !included files have been loaded.

[alvassin]

@dmartinezg got it. thanks!

[dmartinezg]

Here is a sample test, with random response times for includes:

https://github.com/raml-org/raml-js-parser/blob/master/test/specs/regressions.js#L960

[alvassin]

@dmartinezg I implemented support for all !include-d schemas, they work correctly now.

As for inline-specified schemes, that have $refs (see below), I need this issue to be fixed.

After i will get some response from maintainers i will add support for such schemas too.

... raml definition ...
responses:
  200:
    body:
      application/json:
        schema: |
          {
            "$schema": "http://json-schema.org/draft-04/schema#",
            "type": "object",
            "properties": {
              "items": {
                "$ref": "./schemas/collections/items.json"
              }
            }
          }

[alvassin]

@dmartinezg please check code & tests, all cases should be covered now.

[dmartinezg]

@alvassin, apologies for reviewing late, I've had a big mail backlog for the past few days.

I think it is ready to merge, have you signed this?: https://api-notebook.anypoint.mulesoft.com/notebooks#bc1cf75a0284268407e4

After you do that, I can merge, tag and deploy to npm

[alvassin]

@dmartinezg you've got nice automation. Signed.

[dmartinezg]

Oh, please, squash commits

[alvassin]

@dmartinezg done.

[dmartinezg]

@alvassin, thanks!