feat!: deprecate legacy client [NONE] #2317
Draft
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
marcolink
force-pushed
the
major/deprecate-legacy-client
branch
3 times, most recently
from
f97753c
to
d5b5b7b
Compare
marcolink
force-pushed
the
major/deprecate-legacy-client
branch
from
d5b5b7b
to
6191299
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.
Summary
With the next major version (
12.0.0) we finally will deprecate the old client shape.Description
From now on, the old client type will be called legacy
Changes
deprecatedMotivation and Context
The plain client comes with a list of advantages over the legacy client:
ToDo
Checklist (check all before merging)
BREAKING CHANGE: The plain client will become the new default client