Michael Simons

Further update: Investigating the older version it turns out it suffers from the same issue, too.

The behavior is a bit different than the old `@QueryResult`: The query result was basically an arbitrary record. The projection is based on a concrete root object, it's properties are...

In that case, I would consider using the `Neo4jClient` and provide a custom mapping function tbh. See: https://docs.spring.io/spring-data/neo4j/docs/6.1.1/reference/html/#faq.custom-queries-and-custom-mappings 11.9.2

Hey @alxxyz Please see my answer here: https://github.com/spring-projects/spring-data-neo4j/issues/2283#issuecomment-857523868

We give you the freedom and flexibility through the `Neo4jClient` to plug the mapping you want or need. A query result that arbitrary can chose and pick not only from...

The thing is: Repositories in the DDD world are supposed to contain one specific thing and provide CRUD methods for that. That is what a Spring Data Repository does too....

I wouldn't mind extracting a separate module in _this_ project too much. What stands against it is the fact our `@Node`, `@Id` and some other annotations are meta-annotated with Spring...

I see the following issues - The GraphQL library that is referenced by Boot 2.7 is newer than the one supported with the current product. To align both, you'll have...

You made the configurational class bean on its own and you can't auto inject into the overloaded method. I pushed this down, so that the configurer is a bean on...

Closing due to inactivity.