Skip to content

Vue's Sentry.init() options guide needs updating #13157

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
kimulaco opened this issue Mar 30, 2025 · 3 comments · Fixed by #13192
Closed

Vue's Sentry.init() options guide needs updating #13157

kimulaco opened this issue Mar 30, 2025 · 3 comments · Fixed by #13192

Comments

@kimulaco
Copy link

SDK

JavaScript SDK

Description

I think the following documentation needs to be updated about the Sentry.init() configuration options.
https://docs.sentry.io/platforms/javascript/guides/vue/#vue-specific-configuration

  1. The documentation currently includes a logErrors option. However, this has now been removed.
    https://docs.sentry.io/platforms/javascript/guides/vue/migration/v8-to-v9/#removed-apis
  2. attachErrorHandler is implemented in the options of Sentry.init() in vue, but it is not mentioned in the guide.
    https://github.com/getsentry/sentry-javascript/blob/9.10.1/packages/vue/src/types.ts#L29-L57

Suggested Solution

I think the explanation about logErrors should be removed, and an explanation about attachErrorHandler should be added.

@getsantry
Copy link
Contributor

getsantry bot commented Mar 30, 2025

Assigning to @getsentry/support for routing ⏲️

@Lms24
Copy link
Member

Lms24 commented Apr 1, 2025

Hey @kimulaco thanks for reporting this! You're right, we missed a couple of option changes in this page. I opened #13192 and took this as an opportunity to clean up the page a bit in general.

@kimulaco
Copy link
Author

kimulaco commented Apr 1, 2025

@Lms24 Thanks! I appreciate your quick action!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants