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.
What type of change does this PR perform?
Summary
New bug fix release
0.12.1
, which fixes a bug in the duck-typing type check logic and a bug causing thePropertyNotFoundTypeError
error to be thrown as a stand-alone error although it is an error indicating the failure of a parent type check operation.Detailed Changelog
Not present for website/docs changes
Changed
MismatchingArgCountBetweenFuncTypesError
toMismatchingArgCountBetweenFuncTypesTypeError
.UnknownTypeError
toUnknownTypeTypeError
.PropertyNotFoundError
toPropertyNotFoundTypeError
.Fixed
PropertyNotFoundTypeError
being thrown as a stand-alone error instead of being set as the cause for any parentassignment operation failure.
PropertyNotFoundTypeError
being checked for in the wrong direction i.e. thatotherT
had to have all the propertiesof
thisT
instead of the other way around (which is the correct way).str
andArray<T>
being accidentally turned off by incorrect logic. This causedValueTypeNotIndexableWithGivenAccessorTypeError
to be only thrown for objects and not for arrays and strings.Does this PR create new warnings?
None.
Linked issues or PRs
No linked issues.