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

Remove Ambiguous Vue component tracking options #5907

Open
2 tasks
Tracked by #5194
Lms24 opened this issue Oct 7, 2022 · 0 comments
Open
2 tasks
Tracked by #5194

Remove Ambiguous Vue component tracking options #5907

Lms24 opened this issue Oct 7, 2022 · 0 comments

Comments

@Lms24
Copy link
Member

Lms24 commented Oct 7, 2022

Problem Statement

In our Vue SDK, there are two ways how users can set the component tracking-relevant options:

Sentry.init({
  // dsn...
  trackComponents: true,
  timeout: 1000,
  hooks: ['init', 'mount', 'update']
})

Or

Sentry.init({
  // dsn...
  tracingOptions: {
    trackComponents: true,
    timeout: 1000,
    hooks: ['init', 'mount', 'update']
  }
})

Solution Brainstorm

We'd like to remove this ambiguity by

  • 1. [Pre-v8] deprecating one of the two options (i.e. all top 3 level or the tracingOptions options)
    • Our current vote goes to deprecating the top-level options in favour of the tracingOptions object to group component-tracking related options
    • However, the top level options are more prominent in our documentation and hence probably more used
  • 2. [v8] removing the deprecated options and update Sentry docs accordingly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants