-
Notifications
You must be signed in to change notification settings - Fork 7
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
rename JSONRPCError field msg -> message #18
base: master
Are you sure you want to change the base?
Conversation
Codecov Report
@@ Coverage Diff @@
## master #18 +/- ##
======================================
Coverage 3.70% 3.70%
======================================
Files 4 4
Lines 135 135
======================================
Hits 5 5
Misses 130 130
Continue to review full report at Codecov.
|
On the other hand, the Julia exception types all use |
I'm referring to https://github.com/julia-vscode/JSONRPC.jl/blob/master/src/typed.jl#L71 rather than the within-julia error throwing. The receiver of that error message will expect to get a "message" entry won't they? |
The code you link to is a bug, #16 is meant to fix that. We should probably merge that first before we make further changes. |
Do you think we should still do this, or is the current |
It's mildly confusing, may as well change 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.
Cool, sounds good.
I think it also need to be changed at https://github.com/julia-vscode/JSONRPC.jl/blob/master/src/typed.jl#L67.
I don't think any of the downstream packages need an update.
@ZacLN Bump, I think you need to make one more change and then we can merge this. |
msg
was inconsistent with the JSONRPC spec and usage within the package (catch block ofdispatch_msg
).Not clear if this requires downstream changes/version bump?