-
Notifications
You must be signed in to change notification settings - Fork 105
Move payload deserialisation out of handlers #53
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
Move payload deserialisation out of handlers #53
Conversation
This is so the common JsonSerializerSettings can be used by the calling code. NOTE: This code is currently non-functional - handlers have been modified to take an Object instead of a JObject but the calling code does not yet perform deserialisation.
I'm wondering whether |
Codecov Report
@@ Coverage Diff @@
## refactor/protocol #53 +/- ##
====================================================
- Coverage 70.11% 70.02% -0.1%
====================================================
Files 211 211
Lines 2202 2202
====================================================
- Hits 1544 1542 -2
- Misses 658 660 +2
Continue to review full report at Codecov.
|
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.
I learned a long time ago to not fight about naming, 🚲🏠 (bike shedding) goes to far some times.
I think PayloadType
makes more sense, but either name works for me.
Ok - I'm going to change it then 😁 |
Right, have renamed it and added a couple of tests :) Providing CI checks pass, would you like me to add this work to your WIP branch? |
Ok we're good to go :) |
@david-driscoll - I'm going to merge this into your |
This moves the deserialisation of payloads out of handlers and into the calling code (
LspDispatcher
).