Skip to content
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

updates username length to align with the spec (uint8 vs uint16) #938

Merged
merged 1 commit into from
Oct 1, 2020

Conversation

freelancer1845
Copy link
Contributor

Now reads/writes username length as uint16.

The spec was changed in this commit:
rsocket/rsocket@2687daa

I also moved the code of AuthMetdataFlyweightTest to AuthMetadataCodecTest.

Copy link
Member

@OlegDokuka OlegDokuka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@freelancer1845 can you please make sure that you modify only the username length related things and do not touch the rest of the things. It simplifies porting that commit to master then (since in master we have already done the migration from the deprecated classes and removed them completely)

This now follows the new specification.
Test were also moved away from ...Fylweigth to ...Codec

Signed-off-by: Jascha Riedel <Jascha.Riedel@sunplugged.at>
Copy link
Member

@OlegDokuka OlegDokuka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@OlegDokuka OlegDokuka changed the title Updated username length for new spec (uint8 vs uint16) updates username length to align with the spec (uint8 vs uint16) Oct 1, 2020
@OlegDokuka OlegDokuka merged commit 7af1848 into rsocket:1.0.x Oct 1, 2020
@OlegDokuka
Copy link
Member

Thank you @freelancer1845 for this contribution! Keep doing that!

@OlegDokuka OlegDokuka added this to the 1.0.3 milestone Oct 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants