ΘLΞG

@smolinari you brought ups some very interesting points. Though my original intention was more about exposing additional information, rather then a way to aid the data modeling. I would definitely...

@smolinari thanks a lot for a very detailed explanation! I think I can now better understand your point. I would definitely agree with it, there is much more to business...

@wincent > would be a pretty large extension which we would want to evaluate carefully I definitely agree with this! Seeing all these great comments made me think a lot...

@calebmer I definitely think `__Metadata` should be considered a valid alternative. Though I tend to agree with @IvanGoncharov's arguments. So it has it's own set of advantages and disadvantages, like...

@leebyron Thanks a lot for looking into this and giving your feedback! I think we can approach this from 3 different perspectives. First is a semantic meaning of types and...

Just my 5 cents. I would agree with others. I do see demand for JSON/Map but I'm yet to see a good compelling use-case for it (if you look at...

Thanks a lot for starting this discussion, @bbakerman! These are very good discussion points. In my current implementation, I took a quite pragmatic approach. I realize that the decisions that...

just an idea. Maybe it would make sense to introduce special inline fragment semantics for scalars: ```graphql { example { ... on String { value } ... on MyType {...

For modern languages like scala and swift it should be fine as well. But it may cause issues for Java, for instance. This potentially can be problematic for tools like...

Thanks for reporting the issue! Also, the example query would be quite useful. I think the main issue is with the `OverlappingFieldsCanBeMerged` validation. It is one of the most complex...