Christian Beikov

The part `.. and maybe also an integration if needed` is about integrating with the Spring GraphQL module. The Spring Data integration of Blaze-Persistence already supports almost everything that you...

Ok, that's a different thing then. I guess that this is something that will be Spring GraphQL only though, so this kind of depends on an integration with that first,...

Thanks for the clarification. I guess that should be doable :)

We did add support for "injection" of custom parameter types like `EntityViewSettingProcessor` into repository query methods in the past, so I think this is a matter of adding support for...

By suggested you mean that you propose Blaze-Persistence should support this? Because I thought you meant that Spring already has something like that, but couldn't find this in the Spring...

Ok, so here are is concrete proposal: The Spring Data integration should support a `DataFetchingEnvironment` as special parameter type for repository methods. When the return type of the method is...

>So I prefer the second option when I pay a small price (constructing specific EntityViewSetting manually) for greater design flexibility. In fact, the price should be really negligible because paging...

>Oh, I totally missed that 😱 Does it work OOTB with entity views created from DataFetchingEnvironment? I.e. are the queries tailor-made to the input selection set? Unfortunately, doing this requires...

>I would like to have the proposed Allow Spring Data repository methods to accept EntityViewSetting as parameter type, but additionally I would also expect that the possible graphQL selection sets...

Yep, everything should be clear now. Thanks for clarifying.