Redesigned custom methods API with @Query annotation in Repository interfaces:
Instead of specifying the @Tuple annotation (indicated which stack of converters to use) on the methods, we use the output argument in the @Query annotation. Two arguments AUTO or TUPLE can be passed there, which corresponds to the callForObject and callForTuple methods.
Made it so that AUTO can convert tuples too by adding some functionality in callForObject.
Now custom @Query methods always use ReturnType to match the converter stack. DomainType is only used for predefined functions(SimpleTarantoolRepository).
Added an exception if we expect TUPLE, but there is no metadata to convert it. Previously, we just received an empty object and could not figure out what was wrong.
Since we are now looking at returnType we ignore the result if void is specified
Redesigned custom methods API with
@Query
annotation in Repository interfaces:@Tuple
annotation (indicated which stack of converters to use) on the methods, we use the output argument in the@Query
annotation. Two argumentsAUTO
orTUPLE
can be passed there, which corresponds to thecallForObject
andcallForTuple
methods.AUTO
can convert tuples too by adding some functionality incallForObject
.@Query
methods always use ReturnType to match the converter stack. DomainType is only used for predefined functions(SimpleTarantoolRepository
).TUPLE,
but there is no metadata to convert it. Previously, we just received an empty object and could not figure out what was wrong.returnType
we ignore the result ifvoid
is specifiedAlso for details see rfc: #78
Closes #68 Closes #69 Closes #78