Describe the solution you'd like
Right now we expose classes from gRPC and protobuf. We should think about resolving the dependency and hide it's internal implementation to the outside to be "independent" from changes inside the models of the external libraries
Describe alternatives you've considered
Leave it as is
Additional context
evaluate dis-/advantages of re-wrapping the proto files in kuksa-sdk specific domain models. Maybe the effort to convert all proto models into kuksa-sdk specific models is not worth it. It will also mean a lot of effort when a new protocol is released
test if the gRPC dependency in kuksa-sdk can be reduced from api to implementation
aliases can not be used as they are not supported by java
Describe the solution you'd like Right now we expose classes from gRPC and protobuf. We should think about resolving the dependency and hide it's internal implementation to the outside to be "independent" from changes inside the models of the external libraries
Examples are:
gRPC:
Proto:
Describe alternatives you've considered Leave it as is
Additional context