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
As an RSocket-RPC-Java user, I want to have metrics pluggable
Actual Behavior
In the current implementation, metrics are built-in, so it is hardly manageable to eliminate it from the generated code.
Expected Behavior
The current implementation provides proper abstraction and code generation that does not require a user to live with opentracing and micrometer dependencies as an built-in code. In turn, it would be much easier to have an addon to current plugin that can generate adapters for metrics and tracing that could be plugged in as in the following sample:
in that case server/client, impl will be metrics-free code which does the same and adapters code will look like the following (example of generate server adapter):
User Story
As an RSocket-RPC-Java user, I want to have metrics pluggable
Actual Behavior
In the current implementation, metrics are built-in, so it is hardly manageable to eliminate it from the generated code.
Expected Behavior
The current implementation provides proper abstraction and code generation that does not require a user to live with opentracing and micrometer dependencies as an built-in code. In turn, it would be much easier to have an addon to current plugin that can generate adapters for metrics and tracing that could be plugged in as in the following sample:
in that case server/client, impl will be metrics-free code which does the same and adapters code will look like the following (example of generate server adapter):
The text was updated successfully, but these errors were encountered: