-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
feat: expose user astro error #8012
Conversation
🦋 Changeset detectedLatest commit: 56f129b The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
This PR is blocked because it contains a minor
changeset. A reviewer will merge this at the next release if approved.
e26f6c7
to
04286eb
Compare
04286eb
to
1419484
Compare
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'm ok with this approach! But also would like to hear Erika's thoughts if AstroUserError
is a suitable name for this.
Also wonder if it's worth aliasing AstroUserError
to AstroError
during entrypoint re-export to make the API cleaner, but I'm fine either way.
I think aliasing it to AstroError would be fine yeah |
Changes
Adds a new
astro/errors
module, where the user can importAstroUserError
and use it as they see fit.The class accepts a mandatory
message
and an optionalhint
.Testing
N/A
Docs
N/A