refactor!: use events api for utils with compatibility layer#75
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This utility allows interchangeable usage of passing either
req,resoreventto all built-in utilities as bridge to migrate to Events API. (#73)Internally,
toEventHandlerupgrades any handlers that are still in a legacy format and promisify them for compatibility.BREAKING CHANGE: All
handleexports and properties are renamed tohandlerwith some backward compatibilities.BREAKING CHANGE: Legacy handlers are promisified by default
tests are almost untouched to ensure minimum breaking changes