fix(types): ChainablePromiseArray and ChainablePromiseElement resolved to any
#1872
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
dprevost-LMI
commented
Jun 24, 2025
dprevost-LMI
changed the title
ChainablePromiseArray and ChainablePromiseElement resolved to anyChainablePromiseArray and ChainablePromiseElement resolved to any
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As described in the issue, we are fixing
ChainablePromiseArrayandChainablePromiseElementresolved to any caused by the unexpected generics.Also,
jasmine.d.tsstarted to show an error, so I aligned it with the same value asjest.d.tsTo uncover problems in
d.tsfile at the root, I added a tsc command on it as a quick win.