Russell Anthony
Russell Anthony
Commmented on #295 also I'm definitely interested in your progress with this -- custom runtimes with V8 Snapshots sounds like a huge win (but also sounds like something the AWS...
I'm definitely interested in your progress with this -- custom runtimes with V8 Snapshots sounds like a huge win (but also sounds like something the AWS Lambda team easily can...
@MichalLytek how could I create a param decorator that creates an argument without doing it the way I am?
> Your issue is about arg after custom param decorator. I'm not responsible for supporting your patterns like composing decorators and calling them manually. ? It's not my pattern -...
It's worth calling out that when debugging, the provided values are correct when debugging the interceptor for **both** arg1 and arg2 - the values aren't incorrect until the function is...
Also - at runtime the values in getMetadataStorage() are correct - yet the wrong value is being passed to the resolver:
And here is the root of the issue - if I step up into createHandlerResolver, you can see that it is creating three "resolvedParams". My custom parameter is taking index...
After digging in some more, I can see how this isn't currently doable with type-graphql's implementation. The argument will always have two params in ParamMetadata - one with type "arg",...
@MichalLytek here is my proposed solution https://github.com/MichalLytek/type-graphql/pull/1330
> I am also having the same issue. We are trying to modify the incoming object to add the user created and modified at data to one of the args....