feat(unified-api): Define includeLocalVariables option

[AbhiPrasad]

Currently the PHP, Python, Ruby and NodeJS SDKs support local variables, but they all use inconsistent names for the option that gates this functionality.

• Ruby: capture_exception_frame_locals
• Python: with_locals
• PHP no option
• NodeJS _experiments.includeStackLocals

I propose we rename this to includeLocalVariables / include_local_variables, unify these across the SDKs and add them when we get time

We also should decide if sendDefaultPii should have an affect on this.

cc @timfish

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
develop	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Jan 18, 2023 at 4:56PM (UTC)

[antonpirker]

I like consistent naming, so I am in.

As this is only for errors should error be in the variable name? (bikesheding alarm)

[sl0thentr0py]

let's keep the PII stuff separate, I'm working on a comprehensive proposal to solve this better.
If that gets rejected, we can gate locals behind sendDefaultPII later.

[sl0thentr0py]

fine with me, but for existing implementations, we'll have to alias to existing names, deprecate them and remove them later in a major.

[AbhiPrasad]

As this is only for errors should error be in the variable name

This is a good suggestion, but since I think local variables are a stacktrace concept, it should be clear to users that this only applies to errors.

[antonpirker]

Python issue for this: getsentry/sentry-python#1854