Remove all deprecations targeting v4 #244
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
chriskrycho
force-pushed
the
remove-deprecations
branch
2 times, most recently
from
cb7181a
to
3dd48fd
Compare
- Drop all legacy lifecycle hooks from class-based modifiers - Drop defunct options bag for function-based modifiers - Update default type params so unspecified positional arguments are always `[]` and unspecified named arguments are always `EmptyObject`.
chriskrycho
force-pushed
the
remove-deprecations
branch
from
3dd48fd
to
b6624f8
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.
Working on this highlighted a couple improvements to types I have backported as fixes to 3.2 (released as 3.2.1).
We'll target this for release with other breaking changes after dropping Node 12 at the end of April.