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

feat!: change the serializers to use async and streams #158

Merged
merged 1 commit into from
May 1, 2021

Conversation

filipeesch
Copy link
Contributor

Description

  • The IMessageSerializer was renamed to ISerializer
  • The method Serialize was changed to SerializeAsync, to return a Task and writing the result into a Stream
  • The method Deserialize was changed to DeserializeAsync, to return a Task and read the data from a Stream
  • All the existing serializer was changed to use the new interface

Fixes #142

How Has This Been Tested?

The Unit and Integration tests were executed

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have added tests to cover my changes
  • I have made corresponding changes to the documentation

Disclaimer

By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement

@filipeesch filipeesch force-pushed the async-serializers branch 2 times, most recently from cf8df0f to 0455c9a Compare April 30, 2021 09:33
- The IMessageSerializer was renamed to ISerializer
- The method Serialize was changed to SerializeAsync, to return a Task and writing the result into a Stream
- The method Deserialize was changed to DeserializeAsync, to return a Task and read the data from a Stream
- All the existing serializer was changed to use the new interface
@filipeesch filipeesch marked this pull request as ready for review April 30, 2021 15:25
@dougolima dougolima merged commit 592caab into v2 May 1, 2021
@dougolima dougolima deleted the async-serializers branch May 1, 2021 01:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants