-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
fix(doc): surface graph errors as warnings #25888
fix(doc): surface graph errors as warnings #25888
Conversation
pub struct GraphValidOptions { | ||
pub check_js: bool, | ||
pub kind: GraphKind, | ||
pub is_vendoring: bool, |
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.
No need for this anymore.
/// Whether to exit the process for lockfile errors. | ||
/// Otherwise, surfaces lockfile errors as errors. | ||
pub exit_lockfile_errors: bool, | ||
pub exit_integrity_errors: bool, |
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.
Renamed to make it clear that this isn't just for lockfile integrity errors anymore.
@@ -127,8 +129,18 @@ pub async fn doc( | |||
.create_graph(GraphKind::TypesOnly, module_specifiers.clone()) | |||
.await?; | |||
|
|||
if maybe_lockfile.is_some() { |
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.
Should not be conditional on the lockfile because this is overall integrity errors.
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.
LGTM!
Graph errors were being silently ignored.