-
-
Notifications
You must be signed in to change notification settings - Fork 29
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: Join type #1427
fix: Join type #1427
Conversation
Run & review this pull request in StackBlitz Codeflow. |
I think this should do it. I couldn't really reproduce your original issue but, removing the // @ts-ignore reveleaded it as well for me. So now that one is also gone. I've also made sure to add some tests if we need to test that further. So far my custom type assertions were enough but we might should go with something like tsd if we want to do more proper checks. |
ahh ok now I got ya. It doesn't fail in the IDE but when running |
hmm actually it failed when I ran the full Build and after going into the file, I did see the error in the IDE/VSCode as shown in the issue print screen. Also FYI, the reason this came up was that I deleted the pnpm lock file and deleted node_modules, because I wanted get rid of the |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1427 +/- ##
======================================
Coverage 99.8% 99.8%
======================================
Files 199 199
Lines 21611 21611
Branches 7229 7229
======================================
Hits 21547 21547
+ Misses 64 58 -6
- Partials 0 6 +6 ☔ View full report in Codecov by Sentry. |
ok |
I'm a bit surprised, I thought that the lock file was enough to do the update, however I'm not even sure since when this error actually existed. I thought it was the latest TypeScript 5.4 that was released a couple days but as it turns out, the previous version also failed on this type... anyway, as long as we fixed it for the future :) BTW, I saw Cypress failing again so I restarted it |
well if you can't repro it locally and the bundler cant either plus the original intent still is in place ... I'd say we're good until the next time ;) |
Thanks a lot for this PR, you even added more unit tests which is always very welcome... again thx for all your contributions :) BTW, have you had a chance to try the Dark Mode yet? 😉 |
fixes #1422