Eventually captureMessage will be unified with captureException. As a pre-step, we should align behavior between these APIs by defaulting attachStacktrace to true for captureMessage.
Currently captureException always includes a stack trace, while captureMessage only does so when attachStacktrace is explicitly enabled (it defaults to false). Switching this default makes captureMessage behave consistently with captureException, so that unifying them later becomes straightforward.
Eventually
captureMessagewill be unified withcaptureException. As a pre-step, we should align behavior between these APIs by defaultingattachStacktracetotrueforcaptureMessage.Currently
captureExceptionalways includes a stack trace, whilecaptureMessageonly does so whenattachStacktraceis explicitly enabled (it defaults tofalse). Switching this default makescaptureMessagebehave consistently withcaptureException, so that unifying them later becomes straightforward.