Skip to content

Report more error types in the UI #1256

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

Closed
ehmicky opened this issue May 12, 2020 · 2 comments
Closed

Report more error types in the UI #1256

ehmicky opened this issue May 12, 2020 · 2 comments
Labels
stale theme/build-deploy-ux type: feature code contributing to the implementation of a feature and/or user facing functionality

Comments

@ehmicky
Copy link
Contributor

ehmicky commented May 12, 2020

We surface plugin errors in the UI ("plugins error statuses"), i.e. not only in the build logs. We should also show the following specific error types in the UI:

  • netlify.toml configuration error
  • build.command failed
  • internal error in Netlify Build not related to a specific plugin

One thing to consider: error statuses shown in the UI are currently plugin-related. The API endpoint plugin_runs asks for a plugin name, version and the event in which the error happened. This would not fit the errors above, so this would require either adding a new approach for those, or modifying the current approach, for both UI and the API.

Implementation note: in Netlify Build, the logic to retrieve the title, summary and text of error statuses (to send to the API) is not tied to plugins. It works for any error types (including the ones above), so we should re-use the same code we use for plugin error statuses.

@ehmicky ehmicky added the type: feature code contributing to the implementation of a feature and/or user facing functionality label May 12, 2020
@ehmicky ehmicky self-assigned this May 12, 2020
@ehmicky ehmicky removed their assignment Mar 24, 2022
@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has not had activity in 1 year. It will be closed in 14 days if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale label Mar 26, 2023
@github-actions
Copy link
Contributor

This issue was closed because it had no activity for over 1 year.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale theme/build-deploy-ux type: feature code contributing to the implementation of a feature and/or user facing functionality
Projects
None yet
Development

No branches or pull requests

2 participants