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

feat: Add docs about what captureMessage does #11258

Merged
merged 4 commits into from
Sep 18, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/platforms/android/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
2 changes: 2 additions & 0 deletions docs/platforms/apple/common/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
2 changes: 2 additions & 0 deletions docs/platforms/dart/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
2 changes: 2 additions & 0 deletions docs/platforms/dotnet/common/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
2 changes: 2 additions & 0 deletions docs/platforms/elixir/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
2 changes: 2 additions & 0 deletions docs/platforms/flutter/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
2 changes: 2 additions & 0 deletions docs/platforms/go/common/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
2 changes: 2 additions & 0 deletions docs/platforms/java/common/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
2 changes: 2 additions & 0 deletions docs/platforms/javascript/common/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
2 changes: 2 additions & 0 deletions docs/platforms/kotlin-multiplatform/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
2 changes: 2 additions & 0 deletions docs/platforms/native/common/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -34,4 +34,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
2 changes: 2 additions & 0 deletions docs/platforms/php/common/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
2 changes: 2 additions & 0 deletions docs/platforms/php/guides/laravel/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,8 @@ In Laravel, you can pass an error object to `captureException()` to get it captu

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />

## Customization
Expand Down
2 changes: 2 additions & 0 deletions docs/platforms/powershell/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
2 changes: 2 additions & 0 deletions docs/platforms/python/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
2 changes: 2 additions & 0 deletions docs/platforms/ruby/common/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
2 changes: 2 additions & 0 deletions docs/platforms/rust/common/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
2 changes: 2 additions & 0 deletions docs/platforms/unity/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
2 changes: 2 additions & 0 deletions docs/platforms/unreal/usage/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -25,4 +25,6 @@ While capturing an event, you can also record the breadcrumbs that lead up to th

Another common operation is to capture a bare message. A message is textual information that should be sent to Sentry. Typically, our SDKs don't automatically capture messages, but you can capture them manually.

Messages show up as issues on your issue stream, with the message as the issue name.

<PlatformContent includePath="capture-message" />
Loading