-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Type hint support #93
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
I'm not sure if the mustHaveHint
(for vec
) is comprehensive.
Otherwise, just some suggestions.
Ah also, afaict there's no tests? The type hints in the e2e are empty. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RE tests, yeah, I had planned to add them later, just cause I finished this batch of commits later in the day than I'd estimated. Would you want them as part of this PR or a followup?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but please follow-up with tests
closes #92
Extends
fetch
with a--typemap
flag, with which users may submit type hints (described in more detail infetch.ts
), which are used ininstrument
to distinguish vectors from enums, whenv.every((elem) => typeof elem === typeof v[0]
is an insufficient filter condition.Note that all changes to the
.json
files are semantically trivial (a new field with type hits is added)