{"action":"created","issue":{"url":"https://api.github.com/repos/mulesoft-labs/raml-generator/issues/6","labels_url":"https://api.github.com/repos/mulesoft-labs/raml-generator/issues/6/labels{/name}","comments_url":"https://api.github.com/repos/mulesoft-labs/raml-generator/issues/6/comments","events_url":"https://api.github.com/repos/mulesoft-labs/raml-generator/issues/6/events","html_url":"https://github.com/mulesoft-labs/raml-generator/issues/6","id":67242924,"number":6,"title":"Include Schemas in raml context","user":{"login":"justjacksonn","id":10764578,"avatar_url":"https://avatars.githubusercontent.com/u/10764578?v=3","gravatar_id":"","url":"https://api.github.com/users/justjacksonn","html_url":"https://github.com/justjacksonn","followers_url":"https://api.github.com/users/justjacksonn/followers","following_url":"https://api.github.com/users/justjacksonn/following{/other_user}","gists_url":"https://api.github.com/users/justjacksonn/gists{/gist_id}","starred_url":"https://api.github.com/users/justjacksonn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/justjacksonn/subscriptions","organizations_url":"https://api.github.com/users/justjacksonn/orgs","repos_url":"https://api.github.com/users/justjacksonn/repos","events_url":"https://api.github.com/users/justjacksonn/events{/privacy}","received_events_url":"https://api.github.com/users/justjacksonn/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-04-08T23:30:09Z","updated_at":"2015-04-11T02:26:30Z","closed_at":null,"body":"Currently, the schemas defined in the root of a raml file, as well as schemas embedded within the raml file are not accessible in any way via the raml context object.\r\n\r\nIt would be ideal to have a allSchemas (like allResources) option that would be a flat list of all schema files. This should be some form of object though.. because in some cases the schemas are include files, and in others they are inlined. I'd argue against loading up all the include schemas into memory and work towards not using inlined schemas at all, but it is what it is now, so I'd urge that we keep the flat list that includes the type (inline or file) and the actual value (the path/file, or the string of inlined schema). \r\n\r\nThen perhaps for each resource, we have the schema option so that as we iterate a resource, we can access the schema if need be (maybe this is there now? I haven't looked to see if that is possible).\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/mulesoft-labs/raml-generator/issues/comments/91744780","html_url":"https://github.com/mulesoft-labs/raml-generator/issues/6#issuecomment-91744780","issue_url":"https://api.github.com/repos/mulesoft-labs/raml-generator/issues/6","id":91744780,"user":{"login":"blakeembrey","id":1088987,"avatar_url":"https://avatars.githubusercontent.com/u/1088987?v=3","gravatar_id":"","url":"https://api.github.com/users/blakeembrey","html_url":"https://github.com/blakeembrey","followers_url":"https://api.github.com/users/blakeembrey/followers","following_url":"https://api.github.com/users/blakeembrey/following{/other_user}","gists_url":"https://api.github.com/users/blakeembrey/gists{/gist_id}","starred_url":"https://api.github.com/users/blakeembrey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/blakeembrey/subscriptions","organizations_url":"https://api.github.com/users/blakeembrey/orgs","repos_url":"https://api.github.com/users/blakeembrey/repos","events_url":"https://api.github.com/users/blakeembrey/events{/privacy}","received_events_url":"https://api.github.com/users/blakeembrey/received_events","type":"User","site_admin":false},"created_at":"2015-04-11T02:26:30Z","updated_at":"2015-04-11T02:26:30Z","body":"If the schemas loading become an issue to you, please let me know. Right now loading the schema strings is a decision by the current RAML 0.8 parser, but we can look at patching it with additional features when needed."}}