-
-
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
Fix return type of filter
#4
Conversation
Can you look at the tests? |
Yep I'm looking into it. Sorry been in on and off meetings but will have some time in a bit |
all the time in the world, no rush, and let me know if you have Qs! |
So this led me down quite the rabbit hole. As far as I could tell the ts typing was failing even in main. There is some really tricky behavior surrounding the filter option dictating the return type of the inner |
We can go forward with this, but I definitely understand if you would rather just reformat the code or have any other insights. I just wanted to avoid touching the real code if possible. |
any update here? |
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.
Thanks for your patience!
As far as I could tell the ts typing was failing even in main
I see it, weird how that started happening 🤷♂️
An additional consequence of the new type declarations is the unintended export of things like
FilterOrLookup
andFilterOrLookupResponse
This can be “solved” by moving everything to lib/
, and explicitly choosing which types and identifiers to export from index.js
.
I just wanted to avoid touching the real code if possible.
👍
I’ll merge this, and will take a look at the code-style and what to export locally!
Managed to remove a bunch of types that weren’t needed, and was able to get rid of the |
Thanks, released in 2.0.2! |
Fixes #3