#104 @AssertType rejects a promise when used in async methods #105
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.
I've prepared a PR addressing #104
Changes are reflected in tests and in readme:
async and
Promise
returning methodsAssertType
can also work correctly withasync
methods, returning promise rejected withTypeGuardError
To enable this functionality, you need to emit decorators metadata for your TypeScript project.
Then
AssertType
will work with async methods andPromise
returning methods automatically.If you want to throw synchronously for some reason, you can override the behaviour using with
@AssertType({ async: false })
:If you cannot or don't want to enable decorators metadata, you still make AssertType reject with promise using
@AssertType({ async: true })