That is very interesting idea, but i am wondering, couldn't we wrap the internals only so we don't introduce breaking changes?

That is very interesting idea, but i am wondering, couldn't we wrap the internals only so we don't introduce breaking changes?

Adding Context to Response isn’t breaking.
The breaking part is changing the subscription resolver’s return type. We could avoid that by making the feature opt-in with a disabled-by-default parameter.

Unfortunately, I don’t have other ideas on how to propagate the subscription response context up to the interceptors (and beyond) without introducing a breaking change on the resolver.