{"action":"closed","issue":{"url":"https://api.github.com/repos/okgrow/merge-graphql-schemas/issues/24","repository_url":"https://api.github.com/repos/okgrow/merge-graphql-schemas","labels_url":"https://api.github.com/repos/okgrow/merge-graphql-schemas/issues/24/labels{/name}","comments_url":"https://api.github.com/repos/okgrow/merge-graphql-schemas/issues/24/comments","events_url":"https://api.github.com/repos/okgrow/merge-graphql-schemas/issues/24/events","html_url":"https://github.com/okgrow/merge-graphql-schemas/issues/24","id":225754090,"number":24,"title":"Merge Named types","user":{"login":"dyst5422","id":13282627,"avatar_url":"https://avatars0.githubusercontent.com/u/13282627?v=3","gravatar_id":"","url":"https://api.github.com/users/dyst5422","html_url":"https://github.com/dyst5422","followers_url":"https://api.github.com/users/dyst5422/followers","following_url":"https://api.github.com/users/dyst5422/following{/other_user}","gists_url":"https://api.github.com/users/dyst5422/gists{/gist_id}","starred_url":"https://api.github.com/users/dyst5422/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dyst5422/subscriptions","organizations_url":"https://api.github.com/users/dyst5422/orgs","repos_url":"https://api.github.com/users/dyst5422/repos","events_url":"https://api.github.com/users/dyst5422/events{/privacy}","received_events_url":"https://api.github.com/users/dyst5422/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-05-02T16:45:54Z","updated_at":"2017-05-26T15:45:40Z","closed_at":"2017-05-26T15:45:40Z","body":"Seeing as there is a clear namespace conflict for having two similarly named types, I think there is no reason not to merge any named type.\r\n\r\n```graphql\r\ntype MyType {\r\n  name: String\r\n}\r\n```\r\nand\r\n```graphql\r\ntype MyType {\r\n  age: Int\r\n}\r\n```\r\nshould become\r\n```graphql\r\ntype MyType {\r\n  name: String\r\n  age: Int\r\n}\r\n```\r\nbut instead becomes\r\n```graphql\r\ntype MyType {\r\n  name: String\r\n}\r\ntype MyType {\r\n  age: Int\r\n}\r\n```\r\n\r\nThis is less of a concern for these types where you can just use extend, but input types cannot be extended, which makes this string parsing the only way to extend inputs programmatically in the graphql syntax.\r\n\r\n```graphql\r\ninput MyInput {\r\n  name: String\r\n}\r\n```\r\nand\r\n```graphql\r\ninput MyInput {\r\n  age: Int\r\n}\r\n```\r\nshould become\r\n```graphql\r\ninput MyInput {\r\n  name: String\r\n  age: Int\r\n}\r\n```\r\nbut instead becomes\r\n```graphql\r\ninput MyInput {\r\n  name: String\r\n}\r\ninput MyInput {\r\n  age: Int\r\n}\r\n```"}}
{"actor":{"display_login":"RodMachado"}}