Skip to content
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

Set up error reporting for core tooling #20

Open
kscarlett opened this issue Jul 29, 2019 · 0 comments
Open

Set up error reporting for core tooling #20

kscarlett opened this issue Jul 29, 2019 · 0 comments
Labels
area/tooling Categorizes issue or PR as related to the language tooling. feedback wanted kind/feature Categorizes issue or PR as related to a new feature. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Comments

@kscarlett
Copy link
Member

Using a service like sentry.io will give a lot more insight into what some critical errors may be.

There should probably be a flag to get in the config file to disable analytics like this.

@kscarlett kscarlett added enhancement feedback wanted size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jul 29, 2019
@kscarlett kscarlett added this to the v0.6 - Tooling milestone Jul 29, 2019
@kscarlett kscarlett added area/tooling Categorizes issue or PR as related to the language tooling. kind/feature Categorizes issue or PR as related to a new feature. and removed enhancement labels Feb 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tooling Categorizes issue or PR as related to the language tooling. feedback wanted kind/feature Categorizes issue or PR as related to a new feature. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

No branches or pull requests

1 participant