Why `devMode` is marked as `@internal`?

[feinstein]

Problem Statement

devMode is marked as @internal so we get a warning when we try to use it:

  @internal
  bool devMode = false;

Is there a reason for this to be @internal? I can see it being useful to be used as devMode = kDebugMode. This way we get exceptions when we are developing.

Solution Brainstorm

No response

Are you willing to submit a PR?

None

[buenaflor]

@denrase afaik this is one of the issues you worked on, maybe you have more context on this

[denrase]

We just use this internally in test expectations. When enabled, exceptions in user provided closures are re-thrown instead of being swallowed by the SDK. I'm not aware of any effort to make this a public API, so you should not rely on this flag being present in future releases. Maybe @kahest has some thoughts?

[kahest]

As @denrase mentioned, this is not intended or tested to be used outside of automated tests.

@feinstein what is the goal you are trying to achieve? Maybe there is a better way to solve this that is more in line with our SDK design principles.

[feinstein]

Correct me if I am wrong please, as I did a very quick look at the source code. I thought I could set devMode when kDebugMode, so no alerts are sent to Sentry when we are coding and thus generating a bunch of exceptions.

Also to control if exceptions/logs are shown in the console, for development, or are redirected to sentry only for production builds.