Kai Ren

@ilslv yep, you're right. Even if input unions will be introduced, it still won't interfere with deriving input objects on enums. So let's add this ability for 0.16 release.

@Empty2k12 thanks for bringing this up! GraphiQL and GraphQL Playground updates go fully unnoticed for us. I think it's time do to something about it. It would be nice to...

@Empty2k12 grabbing the things only we need (`index.html`) and relying anything else to CDN is OK, imho. There will be too much hassle and unnecessary code bloat in bundling all...

@Empty2k12 > However, I think it will be hard managing the correct versions of dependencies, like when do we update to React 18? I don't think we need require React...

@Empty2k12 if it's missing in the package we can get it directly from GitHub by the package version in `post-install` script and post-process as we need. https://github.com/graphql/graphiql/blob/graphiql%401.9.3/examples/graphiql-cdn/index.html

@Empty2k12 yes. Just to have tracked and streamlined versions management. Manual adjustments won't be the burden once the dependabot creates PR.

@kunjee17 @LegNeato @jmpunkt I think [the new design](https://github.com/graphql-rust/juniper/issues/553#issuecomment-624544235) described in #553 will solve this issue too without providing any flattening capabilities. Simply, it will allow to specify multiple `impl` blocks,...

@kunjee17 it will be incoming feature if community and maintainers will decide so. At the moment it's only a _possible_ incoming feature 🙃 Current `juniper` implemetation doesn't contain such capabilities.

@kunjee17 i think, yes. ```rust enum UnitedApiQueryRoot { Api1(Api1QueryRoot), Api2(Api2QueryRoot), } ``` But at the moment, `juniper` doesn't provide capabilities to derive code for this use case automatically. So, you...

@Ericnr no, I haven't worked on it recently.