You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
which makes it possible to work together with custom media type implementations (JSON:API, Siren, ...) that provide public RepresentationModel<?> API rather than exposing their internal RepresentationModel implementations as public API.
Would it make sense to change the signature of ReactiveRepresentationModelAssembler to
Thanks for filing this, Kai. This looks like an oversight to me. I'll check what the compatibility implications are of this, but I am afraid we at least cause binary incompatibility here. I guess the first version we can ship this in is 2.0 then, as there's no 1.6 release planned anymore.
We now relax the generic bound of D to … extends RepresentationModel<?> as otherwise implementation code of, for example, toModel(…) has to produce a concrete representation model and cannot be typed to return RepresentationModel<?>.
On the other side, I would expect this to be a backward-compatible change, that could potentially also applied to 1.5.x. But I am NOT an expert in this, and it is probably not worth spending much time investigating :)
The current signature of
ReactiveRepresentationModelAssembler
isThe non-reactive
RepresentationModelAssembler
has the signature:which makes it possible to work together with custom media type implementations (JSON:API, Siren, ...) that provide public
RepresentationModel<?>
API rather than exposing their internalRepresentationModel
implementations as public API.Would it make sense to change the signature of
ReactiveRepresentationModelAssembler
to?
This would have the following 2 advantages:
RepresentationModelAssembler
sThe text was updated successfully, but these errors were encountered: