Jordan Stout

@19majkel94 bummer, yeah looks like most "code first" node.js implementations are going to have a rough time from what I was reading. I saw a post of someone requesting a...

https://github.com/prisma/nexus/issues/148 for reference

@19majkel94 that sounds pretty flexible? Also, again, I haven't dug into how to do it within your library. Are you looking at the SDL `apollo-federation` came up with? Or the...

Another issue to help solve code first libraries: https://github.com/apollographql/apollo-server/issues/2769

Another note I saw regarding "extends". https://www.apollographql.com/docs/apollo-server/federation/federation-spec/ The spec actually supports this: ```graphql type User @key(fields: "id") @extends { id: ID! @external reviews: [Review] } ``` But still looks like...

Sorry, @19majkel94 saw that there was an issue relating to simple stuff. I too have the need for simple stuff in many cases. His example is on the ad side...

I'd suggest keeping this out of this library and somehow (if custom decorator support,or similar, is made) make it so that 3rd parties can connect two different metadata libraries together....

@19majkel94 I haven't looked into ttypescript, but does the compiler support decorators on interfaces? It would be so nice to pass vanilla objects and use field resolvers to do "magic"...

The above code example are classes backed by interfaces. I want to use type-graphql on existing classes without having to wrap them to setup fields, etc.

@cramhead that's pretty dang cool. It's sort of what I was thinking originally. I've since moved my models to my graph layer and with apollo federation coming soon, will be...