-
Notifications
You must be signed in to change notification settings - Fork 780
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: update definitions for tsc 2.6, fixes #618 #619
fix: update definitions for tsc 2.6, fixes #618 #619
Conversation
i'm still depending on |
If you have a moment, a quick review would be much appreciated. Thanks! |
Looks perfect to me 👍 |
Awesome, this has been added to our backlog for final review and merge. |
@thinkingserious i've also sent #621 to fix the CI, i don't know if it's still required but 11 days ago was needed to make the CI work again. |
Been almost 3 weeks now. Any ETA on getting this small fix merged? |
Hi, I also need to merge this PR to deploy to prod |
+1 need this PR. |
Hello @ShaharHD @joseSantacruz @wwwy3y3, This PR is on our backlog, which we are working through from oldest to newest. Our backlog is a bit overloaded because of Hacktoberfest, tub we are currently working to get caught up. My apologies for the delay and I do appreciate your support and patience. With Best Regards, Elmer |
Thanks for taking the time to check it out @jdanyow! |
@thinkingserious Why wasn't this included in |
hopefully i can continue to ship to production thanks to quickfix. ✌️ @ShaharHD @thinkingserious @spartan563 this PR should be merged ASAP because doesn't have any conflicts or regressions and fixes problems with typescript 2.6, so i don't see any reason to not merge this! |
Thanks @phra! I have this on my list to deploy today. |
Hi @phra, Before I merge this, could you please take a look at this recently merged PR to see if any further TypeScript changes are necessary? Thanks! With Best Regards, Elmer |
It looks like there are some changes that are necessary to align it with the newly exported module spec. Specifically, rather than simply exporting Should be a pretty easy fix. |
i will do it later today. 👍 |
done. can you review the code? @thinkingserious @spartan563 |
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 good to me 👍 thanks @phra
Thanks to @phra and @spartan563 for being AWESOME and getting this done so quickly! I should have this deployed no later than tomorrow. |
@thinkingserious waiting for this pr to be merged. When will it be done? |
I'm shooting for some time today. |
Thanks for fixing this 👍 I can now set the compiler back to strict mode 😄 |
Awesome, thanks for the comment @0x80! |
Hey @phra, |
@hansenst at the time of committing, it was working properly. can you check it using tsc version ~2.6 ? i can eventually send another PR fixing it if it doesn't break v2.6 release or look for a solution that can work on tsc 2.6 and newer versions. |
Sorry @phra, I was somewhat unclear in my comment. Typescript itself is happy with the current types, but calling the We're currently using TS 2.8.3. |
i've updated the definitions files to support typescript 2.6. fixes #618