-
-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add a close overload for jsonrpcpluginv2 #2700
Conversation
} | ||
catch (Exception e) | ||
{ | ||
Log.Exception( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the case where the plugin hasn't imemted the 'close' method? If so do we need to be logging it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not the case that plugin didn't implement the close
method. This part is for all other excpetions, which we should log it or throw it maybe? well I guess it's better to just rethrow it.
That is the previous exception branch. I don't think we really need to log it, because if plugin doesn't have the close method, we can safely assume that they don't need it. Further, given that we already release jsonrpc v2 even though without documentation and as prerelease, it may be a problem to break the backward compatibility. And it doesn't gain us anything for logging it, unless we mark it as exception?
LGTM, just remove the Logger import since you're no longer logging anything. |
Send a request to jsonrpcv2 when flow is closing.