ARROW-4442: [JS] Add explicit type annotation to Chunked typeId getter #3538
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.
Closes https://issues.apache.org/jira/browse/ARROW-4442
Typescript is generating an overly broad type for the
typeId
property of the ChunkedVector class, leading to a type mismatch and failure to inferChunked<T>
is aVector<T>
:The type being generated currently is:
but it should be:
The fix is to add an explicit return annotation to the Chunked
typeId
getter. Unfortunately this only affects the generated typings (.d.ts
files) and not the library source, so it's difficult to test. We can look into whether there are any flags to trigger stricter type checking of the compiled code in the unit tests, but I don't know any off the top of my head.