-
Notifications
You must be signed in to change notification settings - Fork 471
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
telemetry(amazonq): add metric for transformation type #6284
base: master
Are you sure you want to change the base?
Conversation
|
await this.messenger.sendSelectSQLMetadataFileMessage(message.tabID) | ||
} | ||
} catch (err: any) { | ||
getLogger().error(`Error handling SQL conversion: ${err}`) |
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.
Note: if the exception is caught then run()
won't reflect a result=Failed
.
If handleSQLConversion
is called from a command or webview, the extension global handler will log the error and show a useful message to the user. If not, then the next best approach is to let the exception through, but add .catch(...)
to the run()
call.
Same for the other case in this PR.
Problem
Be able to tell when a language upgrade vs sql conversion happens.
Solution
Add metric.
feature/x
branches will not be squash-merged at release time.