Lukas Ender

@steinroe thanks a lot! 🙏 Invite sent. There's only one Pull Request in that repo. I hope it explains everything with enough detail. If not, feel free to leave questions...

Yes, thanks a lot again! The first test in the example repo verified it should be fixed https://github.com/doug-martin/nestjs-query/pull/1353#issuecomment-926434661 I'll be waiting for the new release and then test it with...

@steinroe @doug-martin I've tested the new version v0.30.0 and in my larger codebase and the problem still occurs. I'm trying to fully understand the issue and come up with an...

@steinroe As far as I can tell, it's only ever the "root-DTO" and its authorizer (in my example, the one of `ResourceA`). If it then tries to authorize relations, it...

@steinroe @doug-martin As discussed, I've prepared an example and showcase https://github.com/lukasender/nestjs-query/pull/1 I've created the example in the `nestjs-query/examples/auth-depth` (I'm lacking a better name right now) folder and created an `e2e`...

Option 1 sounds like a breaking change (e.g. lose the ability to overwrite relation authorisation) with quite some implications when forcing one to enable `fieldResolverEnhancers`, wouldn't it (i.e. breaking changes,...

@MikeMatrix I have a similar situation. Did you figure it out or what's the best way to deal with this?

@mikefowler thanks for the fast response. Refactor as you want :) Also, I'm not sure if it is the best solution to let a user specify groups. It is rather...

Hey @mikefowler :) Thanks for the follow up. If I understand you correctly, it'll allow you to only specify one "point" for each marker, is that correct? Imho, that would...

Hello everyone 👋 I stumbled into the same „trap“ it seems. I wanted to use subscribers to know which entity was updated so I can react on it and inform...