Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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: recover from smoldot crashes #2162
fix: recover from smoldot crashes #2162
Changes from all commits
6f8cbe0
2b137df
b7695b1
83c13c1
5dbdd8d
9aef16a
b5c94aa
f060e92
8d9257f
ae172e0
26c55e7
0092711
1108039
262bf61
7d3f498
7540cd2
885904c
a407a26
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I know that this pattern exists throughout the repo, but IMO I think it'd be better practice to be explicit about the exports from a package rather than use * exports (just so the library interface is obvious just looking at this root file and not needing to traverse other stuff :)
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.
Yeah but I find its really easy to forget to add a new type that should get re-exported and then it gets missed during code review because people don't really pay attention to that.
For anything that should be kept 100% internal I like to use the
@internal
jsdoc tag and then withstripeInternal
settrue
in your tsconfig, these definitions won't be included in the d.ts`https://www.typescriptlang.org/tsconfig/#stripInternal
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.
Yup totally true; we forget to export types in Rust a fair bit, but personally I much prefer to forget exporting a type than to accidentally export a type I didn't mean to; it's easier to go one way than the other! But mainly it just makes it super easy at a glance to see what's being provided by the package.
TIL about
@internal
; that's cool to know about! Ultimately I'm not super fussed about this so happy to stick with the *'s +@internal
's if you prefer that way around!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.
Gonna opt for the YOLO approach and just use @internal.
But if you want to actually see what the publicly export types are u can run
corepack pnpm turbo build
then open thedist
folder and each of the the subpath exports will have ad.ts
file in it showing the public api.This file was deleted.