fix: adds support for assertion functions #25
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
|
Thanks, assertion functions did not exist when I wrote this. Will pick this up when I can 👍 |
|
Hey, thanks for the quick response. Love the plugin by the way! |
|
I validated this change against a fairly big codebase, and everything worked as expected. |
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.
Description (What)
This PR adds support for assertion functions. Assertion functions are not available as arrow functions (see microsoft/TypeScript#34523).
Fixes #22
Justification (Why)
Because we're not supposed to be converting assertion functions to arrow functions.
How Can This Be Tested?
yarn testalwaysValid(function foo(val: any): asserts val is string {}) should pass on the test