-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Fix BuildActionTelemetryTable tool #61795
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
Conversation
Follow up to dotnet#60480. The above PR led to us logging provider name instead of code action name in the telemetry when provider is using CodeAction.Create helper to create a code action. This broke the CodeActionDescriptionMap within the BuildActionTelemetryTable tool that is used to search for code action telemetry in Kusto. This PR regenerates the CodeActionDescriptionMap. I have added a helper method to the tool which can be used when required to regenerate this description map in future.
JoeRobich
left a comment
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.
Thanks for this change. Just needs a little cleanup of the generated descriptions.
Co-authored-by: Joey Robichaud <[email protected]>
Seems like a fully automated approach to generate descriptions is not completely feasible. Hopefully, we don't need to refresh this table too often. |
Follow up to #60480.
The above PR led to us logging provider name instead of code action name in the telemetry when provider is using CodeAction.Create helper to create a code action. This broke the CodeActionDescriptionMap within the BuildActionTelemetryTable tool that is used to search for code action telemetry in Kusto.
This PR regenerates the CodeActionDescriptionMap. I have added a helper method to the tool which can be used when required to regenerate this description map in future.