-
Notifications
You must be signed in to change notification settings - Fork 25
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
UUID serializer and its unit test #139
UUID serializer and its unit test #139
Conversation
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.
For the most part, this looks good. I left a comment about the string format with a link to the relevant RFC, and suggested some additional test cases. Let me know if you have any questions.
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'm ok with this. There is one small note on a test case.
I don't think we should hold up the PR while we decide if we need the byte serializer.
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.
Ok, I actually have just one more change to ask for. Can you rebase this onto main (make sure it is the latest main from eclipse-uprotocol/up-cpp and not your fork) so that the CI can run?
While you are doing that, I would also appreciate it if you could use interactive rebase to squash your commits and clean up the commit messages. You don't have to squash down to one commit - whatever number clearly shows the units of work.
This article provides some good guidance on commit messages.
3ad819f
to
f9dc8fd
Compare
sounds good, I will squash to couple of commits |
a914773
to
da2fb91
Compare
da2fb91
to
5fa979a
Compare
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.
LGTM
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.
Mostly nitpicks - use your best judgement on those.
On the tests, looks great, I liked your use of sequential (expected, easy-to-identify) strings.
5fa979a
to
5a9a87c
Compare
Thank you, I've updated PR with the suggested changes |
No thank you. Looks great - thanks for the extra effort. Approved! |
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.
Looks good to me. Can you make sure that the commits are rebased so that the conan change is dropped? It should already be committed to main. Otherwise this is ready to go.
This PR adds uuid serializer for uprotocol uuid v8 AsString::serialize -> serializes uuid as string in human redable format AsString::deserialize -> deserializes string format uuid AsBytes::serialize -> serializes uuid as bytes AsBytes::deserialize -> deserialize uuid byte The serialization and deserialization as byte checks the endianess and makes sure uuid field are populated correctly
5a9a87c
to
e80a719
Compare
This PR adds UUID serializer for uprotocol uuid v8 #122