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
Currently both clients (sdk and mirrorNode) can send a variation of errors.
These leak info, make logs large and also vary in nature so it's hard to sometime differentiate and infrom how the eth_x calls should handle them.
Solution
We should add a SDKClientError and MirrorNodeClientError class that consumes the returned errors and captures the value information e.g. type, status code etc.
This should be thrown by the clients, checked for by eth class and managed as needed.
This way server logs and details are very small and specific and don't leak eth or client info
Alternatives
No response
The text was updated successfully, but these errors were encountered:
Problem
Currently both clients (sdk and mirrorNode) can send a variation of errors.
These leak info, make logs large and also vary in nature so it's hard to sometime differentiate and infrom how the
eth_x
calls should handle them.Solution
We should add a
SDKClientError
andMirrorNodeClientError
class that consumes the returned errors and captures the value information e.g. type, status code etc.This should be thrown by the clients, checked for by
eth
class and managed as needed.This way server logs and details are very small and specific and don't leak
eth
or client infoAlternatives
No response
The text was updated successfully, but these errors were encountered: