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(gatsby-cli): Fine-grained errors with type/category #37070
Conversation
type: `UNKNOWN`, | ||
level: `ERROR`, |
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.
Since both are optional for plugins (current behavior) but required internally, we're setting default values here
type: Type.WEBPACK, | ||
// TODO: The type needs to be better | ||
type: Type.UNKNOWN, |
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.
Is this because the error could be for bunch of different webpack stages and because of that we can't assign type here? For the follow up we would create specific code ids for each stage then?
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.
Correct. We'd need to make type
also optionally accept the context
so that we can for each stage have an error
Description
Forces the existence of
type
andcategory
on our internal errorMap. Makes thetype
more fine-grained.Documentation
No public API changes, so no docs changes needed.
Related Issues
[ch58451]
[ch58452]