The API v1 and v2 implementations of the following components currently share common behaviour by inheriting common base classes. It is preferable to share these by delegation to avoid awkwardness of deprecation/de-implementation and incompatible API signatures as the v2 API evolves and in the future other versions (2.1, 3.0, ...?) are added.
ModelServerClient interface and implementation classes
If we pull out an abstract client which is extended by V1 and V2 then we should pull out parameters. Otherwise this is weird imho.
_Originally posted by @eneufeld in https://github.com/eclipse-emfcloud/emfcloud-modelserver/pull/151#discussion_r800438406_
The API v1 and v2 implementations of the following components currently share common behaviour by inheriting common base classes. It is preferable to share these by delegation to avoid awkwardness of deprecation/de-implementation and incompatible API signatures as the v2 API evolves and in the future other versions (2.1, 3.0, ...?) are added.