Add support for fluent QueryResultConverter
#4949
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We now support configuring a
QueryResultConverter
that has access to the raw resultDocument
and the mapped result object that has been materialized fromMongoConverter
:This is useful to either wrap, post-process results contextually or apply further transformations based on the result
Document
. Changes apply for imperative and reactive find, geoNear and aggregations.TODO:
QueryResultConverter.entity()
(returning the converted object) is a good naming fit for queries, but with projections or aggregations we might to name it differently