-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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, lints in example #2518
Conversation
Signed-off-by: Karl Horky <karl.horky@gmail.com>
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Signed-off-by: Karl Horky <karl.horky@gmail.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #2518 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 23 23
Lines 2693 2712 +19
Branches 2 2
=========================================
+ Hits 2693 2712 +19 ☔ View full report in Codecov by Sentry. |
Co-authored-by: Titus <tituswormer@gmail.com> Signed-off-by: Karl Horky <karl.horky@gmail.com>
thanks! |
Can you try and build the website next time btw? That actually type checks. And finds other problems, such as that toml wasn’t registered, and that your example uses typescript instead of javascript! 05ecf65 |
Ah, sorry for the multiple mistakes there 😬 I am actually working on GitHub only, I don't even have this cloned - just relying on GitHub Actions CI and my memory / reviewing to do the right thing. Would it make sense to add a "smoke test" website build to the GitHub Actions CI? For my own PRs for now, I'll keep in mind that things can break without being reported by CI. |
Don’t worry about it! It's intentional that things don't break, so newcomers can contribute, even when they're not as neat in their code as the maintainers! Or, a type error can exist for a bit in an example, while the website remains maintainable. |
Initial checklist
Description of changes
Small follow-up to #2517 to address the type checking and linting problems with the original code from the Bun docs