-
Notifications
You must be signed in to change notification settings - Fork 77
json-schema integration not up to the spec #76
Comments
So i dug a little more. Seems no parser does the full job and this library has a second parameter that avoids parsing the schemas. Still it would be cool to be the only parser to do this, so it may be a nice new feature. |
If there's enough demand then we'll implement it, and if you'd like that feature immediately, you can always make a pull request. There's a couple pull requests from my repo waiting incorporation, so to keep things stable, I'd suggest waiting until those are merged. |
Hi Rafael, I agree it's a problem, however I'm not currently sure how to fix it. Either the order in which the schema's were listed would have to become important - which feels like a dodgy thing to do with an unordered array! Or you would have to parse them twice - which feels like it could get pretty complicated. Not sure what to suggest - but open to ideas |
Scenario:
Using the above example i should get a valid result to navigate (raml successfully parsed), and (as a bonus) my json-schema would load the email entity inside the account emails property.
However it tries to load
email
as if its a remote json-schema fileI believe this is an issue in how processing is handed over to json-schema but i'm not entirely sure where the blame lies.
I tried other RAML parsers:
in the
schemas
property $ref was also not expanded.Is there an option to avoid the complete crash and just keep going with the superficial data from schema?
The text was updated successfully, but these errors were encountered: