Jordan Stout

Eeks, I've never considered a GraphQL resolver to be a controller. GraphQL !== MVC. GraphQL === GraphQL. :P

@MichalLytek I was going to try to help with allowing support for nested inputs (I feel that inputs are almost pointless if they don't convert to what a user would...

Classes are unmaintainable when they start doing too much. FP is unmaintainable when you have a single function trying to do too much. But to each their own :P

I'll play with some ways of doing what you've said above in the current code base. Non-nested inputs is kind of blocking at the moment which is super frustrating. And...

The one thing I'm trying to think about if that recursion and type checking is done on the resolver, you're having to check if a field is an input type...

@MichalLytek Yeah, I don't use `class-transform` either. https://github.com/j/type-mongodb I do it my own way here. I've had issues as well with `class-transform`. Constructing nested input types *shouldn't* be hard. I...

> All I can think of is to prefetch the types info and build something like a conversion tree that we can then traverse in runtime mapping the args object...

> // TODO: refactor to map for quicker access Haha, okay, cha-chingggg. I wrote a simple test and got nested inputs to work with arrays & non-arrays, but then I...

@MichalLytek https://github.com/MichalLytek/type-graphql/pull/452 does the job. I can add more tests on caching, etc too. I just got it to work while not breaking anything.

Yup, exactly. I enjoyed zeits stuff and was lambda is a comforting move. We had some stuff in production that went down many times and came running back to Up....