-
-
Notifications
You must be signed in to change notification settings - Fork 625
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(types): correct TypeCast's Next callback to return unknown #3129
Conversation
Fixes typeCast Next type appears to be incorrect sidorares#3122
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3129 +/- ##
=======================================
Coverage 88.13% 88.13%
=======================================
Files 71 71
Lines 12890 12890
Branches 1355 1355
=======================================
Hits 11361 11361
Misses 1529 1529
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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, @bbugh.
I've suggested some rollback changes to the website's test files, or if you prefer, the CI error is due to the last EOL character in ./website/test/fixtures/external-code-embed/QueryOptions.txt
🤝
@wellwelwel I reverted the fixture files, it appears to be passing the checks now. Sorry for the trouble! |
Thanks again, @bbugh 🙋🏻♂️ |
Fixes "typeCast Next type appears to be incorrect" #3122
Also replaced references to the old incorrect type signature in referencing comments