-
Notifications
You must be signed in to change notification settings - Fork 2
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
Prepare release of 0.5.0 #59
Conversation
i think we're ready to merge and release! |
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.
👍
@@ -81,6 +81,9 @@ export const TypescriptHover = { | |||
} | |||
return undefined; | |||
} catch (err) { | |||
// NOTE - This could happen because of an error in other TS plugins | |||
// I.e., we could end up propagating errors from other plugins | |||
// (This happened to me with the tailwind intellisense plugin) |
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 was thinking: Is there a way where we can better expose the exact error the user?
It seems like we can't show multiline notifications (see microsoft/vscode#101589) but perhaps we could do something where we add a "details" button so the user can find out more information around the exact error (which might help us resolve issues faster)
The @autometrics/typescript-plugin. This is done just be make sure that people use the (current) latest release of the typescript plugin.
Notes
I hit a few issues when doing a QA pass over the course of a few days:
Clicking on a function in the Autometrics side bar will open a new tab for that function, but the graphs won't appear (Clicking on a function in the Autometrics side bar does not show full graphs page #62)
Typescript tooltips broke for me in another project (fiberplane-charts) — the Autometrics extension threw an error, even in a project that did not have autometrics, so, the tooltips for a general typescript type just would not appear. (Noted this in an issue, as the culprit was another extension: 🐛 Errors from other Typescript extensions can cause Autometrics to show a toast error notification #63)
Latency queries did not work with my sample Python app (fixed in Support renamed metrics (and fix build_info queries) #61)
Integrated charts throw an error when fetching data from
am
prometheus (fixed in Replace provider with typescript client for querying prometheus data #60)