{"action":"created","issue":{"url":"https://api.github.com/repos/swagger-api/swagger-spec/issues/377","labels_url":"https://api.github.com/repos/swagger-api/swagger-spec/issues/377/labels{/name}","comments_url":"https://api.github.com/repos/swagger-api/swagger-spec/issues/377/comments","events_url":"https://api.github.com/repos/swagger-api/swagger-spec/issues/377/events","html_url":"https://github.com/swagger-api/swagger-spec/issues/377","id":80711545,"number":377,"title":"Allow anyOf in specification","user":{"login":"paulhill","id":754053,"avatar_url":"https://avatars.githubusercontent.com/u/754053?v=3","gravatar_id":"","url":"https://api.github.com/users/paulhill","html_url":"https://github.com/paulhill","followers_url":"https://api.github.com/users/paulhill/followers","following_url":"https://api.github.com/users/paulhill/following{/other_user}","gists_url":"https://api.github.com/users/paulhill/gists{/gist_id}","starred_url":"https://api.github.com/users/paulhill/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/paulhill/subscriptions","organizations_url":"https://api.github.com/users/paulhill/orgs","repos_url":"https://api.github.com/users/paulhill/repos","events_url":"https://api.github.com/users/paulhill/events{/privacy}","received_events_url":"https://api.github.com/users/paulhill/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-05-25T23:53:52Z","updated_at":"2015-05-26T14:15:54Z","closed_at":null,"body":"We don't necessarily need to support anyOf for tooling. \r\nI know the code generation authors like the definition of type hierarchy that comes with allOf inheritance. \r\nBut it would be so nice to be able to specify an anyOf array.\r\nEven if swagger spec validation just ignored it that would be an improvement.\r\nIt seems so restrictive to disallow certain types of schema validation just because tool authors aren't supporting it.\r\n\r\n:-/"},"comment":{"url":"https://api.github.com/repos/swagger-api/swagger-spec/issues/comments/105539035","html_url":"https://github.com/swagger-api/swagger-spec/issues/377#issuecomment-105539035","issue_url":"https://api.github.com/repos/swagger-api/swagger-spec/issues/377","id":105539035,"user":{"login":"webron","id":241629,"avatar_url":"https://avatars.githubusercontent.com/u/241629?v=3","gravatar_id":"","url":"https://api.github.com/users/webron","html_url":"https://github.com/webron","followers_url":"https://api.github.com/users/webron/followers","following_url":"https://api.github.com/users/webron/following{/other_user}","gists_url":"https://api.github.com/users/webron/gists{/gist_id}","starred_url":"https://api.github.com/users/webron/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/webron/subscriptions","organizations_url":"https://api.github.com/users/webron/orgs","repos_url":"https://api.github.com/users/webron/repos","events_url":"https://api.github.com/users/webron/events{/privacy}","received_events_url":"https://api.github.com/users/webron/received_events","type":"User","site_admin":false},"created_at":"2015-05-26T14:15:54Z","updated_at":"2015-05-26T14:15:54Z","body":"Actually, we necessarily need to support it. \r\n\r\nWhile strictly speaking, Swagger is the specification, the specification itself means nothing without proper tooling support.\r\n\r\nWhile you may not be looking it, once we put it in, users would start asking for it (and rightfully so). This is true for other features that are not yet fully implemented in the tools (though are easier to implement).\r\n\r\nWe're trying to think of ways to add support for anyOf in the future though."}}