Add conveniences to PSQLFrontendMessage #173
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gwynne
approved these changes
Sep 18, 2021
Co-authored-by: Gwynne Raskind <gwynne@darkrainfall.org>
fabianfett
force-pushed
the
ff-messages
branch
from
eeb38a6 to
f0f62e9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
We want to use the
NIOSingleStepByteToMessageDecoderwithin thePSQLChannelHandlerin the future. For this reason it is important that we will be able to decode PSQLFrontendMessages for tests in the future.Changes
PSQLFrontendMessagePayloadEncodabletoPSQLMessagePayloadEncodablePSQLFrontendMessage.IDis nowRawRepresentableResult
Code that makes testing easier in the future.
Note: Please don't auto release this. Follow up prs incoming.