Deprecate ContentCodec API with offest & length #1440
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
|
Build failure due #1323 |
idelpivnitskiy
approved these changes
Mar 16, 2021
...alk-encoding-netty/src/main/java/io/servicetalk/encoding/netty/NettyChannelContentCodec.java
Outdated
Show resolved
Hide resolved
...encoding-netty/src/test/java/io/servicetalk/encoding/netty/NettyChannelContentCodecTest.java
Show resolved
Hide resolved
bondolo
pushed a commit
to bondolo/servicetalk
that referenced
this pull request
Mar 16, 2021
* Deprecate ContentCodec API with offset & length
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:
Deprecate the
ContentCodecAPIs that receive offset & length. User's can slice if needed.Modifications:
Deprecate API & relevant changes to accommodate the change.
Result:
Less API surface.