Skip to content

Commit 8d2b31a

Browse files
authored
chore: Added docs to CaptureFeedback (#2715)
1 parent ab76cfe commit 8d2b31a

1 file changed

Lines changed: 45 additions & 0 deletions

File tree

src/Sentry.Unity/SentrySdk.Dotnet.cs

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -313,13 +313,31 @@ public static SentryId CaptureMessage(string message, Action<Scope> configureSco
313313
/// <summary>
314314
/// Captures feedback from the user.
315315
/// </summary>
316+
/// <param name="feedback">The feedback to send to Sentry.</param>
317+
/// <param name="configureScope">The callback to configure the scope.</param>
318+
/// <param name="hint">An optional hint providing high-level context for the source of the event.</param>
319+
/// <returns>The Id of the captured feedback. Returns <see cref="SentryId.Empty"/> when capture failed.</returns>
316320
[DebuggerStepThrough]
317321
public static SentryId CaptureFeedback(SentryFeedback feedback, Action<Scope> configureScope, SentryHint? hint = null)
318322
=> Sentry.SentrySdk.CaptureFeedback(feedback, configureScope, hint);
319323

320324
/// <summary>
321325
/// Captures feedback from the user.
322326
/// </summary>
327+
/// <param name="feedback">The feedback to send to Sentry.</param>
328+
/// <param name="result">
329+
/// The outcome of capturing the feedback. <see cref="CaptureFeedbackResult.Success"/> means the
330+
/// feedback was accepted and handed to the transport. It passed validation and event processors and
331+
/// was queued for delivery. It does <b>not</b> confirm that the feedback was transmitted to Sentry.
332+
/// </param>
333+
/// <param name="configureScope">The callback to configure the scope.</param>
334+
/// <param name="hint">An optional hint providing high-level context for the source of the event.</param>
335+
/// <returns>The Id of the captured feedback. Returns <see cref="SentryId.Empty"/> when capture failed.</returns>
336+
/// <remarks>
337+
/// Capturing is asynchronous and non-blocking. The envelope is handed to a background worker. Non-success
338+
/// results inform only on whether the capture succeeded or failed on the client, i.e. empty message,
339+
/// disabled SDK, dropped by an event processor.
340+
/// </remarks>
323341
[DebuggerStepThrough]
324342
public static SentryId CaptureFeedback(SentryFeedback feedback, out CaptureFeedbackResult result,
325343
Action<Scope> configureScope, SentryHint? hint = null)
@@ -328,13 +346,31 @@ public static SentryId CaptureFeedback(SentryFeedback feedback, out CaptureFeedb
328346
/// <summary>
329347
/// Captures feedback from the user.
330348
/// </summary>
349+
/// <param name="feedback">The feedback to send to Sentry.</param>
350+
/// <param name="scope">The scope to apply to the feedback.</param>
351+
/// <param name="hint">An optional hint providing high-level context for the source of the event.</param>
352+
/// <returns>The Id of the captured feedback. Returns <see cref="SentryId.Empty"/> when capture failed.</returns>
331353
[DebuggerStepThrough]
332354
public static SentryId CaptureFeedback(SentryFeedback feedback, Scope? scope = null, SentryHint? hint = null)
333355
=> Sentry.SentrySdk.CaptureFeedback(feedback, scope, hint);
334356

335357
/// <summary>
336358
/// Captures feedback from the user.
337359
/// </summary>
360+
/// <param name="feedback">The feedback to send to Sentry.</param>
361+
/// <param name="result">
362+
/// The outcome of capturing the feedback. <see cref="CaptureFeedbackResult.Success"/> means the
363+
/// feedback was accepted and handed to the transport. It passed validation and event processors and
364+
/// was queued for delivery. It does <b>not</b> confirm that the feedback was transmitted to Sentry.
365+
/// </param>
366+
/// <param name="scope">The scope to apply to the feedback.</param>
367+
/// <param name="hint">An optional hint providing high-level context for the source of the event.</param>
368+
/// <returns>The Id of the captured feedback. Returns <see cref="SentryId.Empty"/> when capture failed.</returns>
369+
/// <remarks>
370+
/// Capturing is asynchronous and non-blocking. The envelope is handed to a background worker. Non-success
371+
/// results inform only on whether the capture succeeded or failed on the client, i.e. empty message,
372+
/// disabled SDK, dropped by an event processor.
373+
/// </remarks>
338374
[DebuggerStepThrough]
339375
public static SentryId CaptureFeedback(SentryFeedback feedback, out CaptureFeedbackResult result,
340376
Scope? scope = null, SentryHint? hint = null)
@@ -343,6 +379,15 @@ public static SentryId CaptureFeedback(SentryFeedback feedback, out CaptureFeedb
343379
/// <summary>
344380
/// Captures feedback from the user.
345381
/// </summary>
382+
/// <param name="message">The feedback message.</param>
383+
/// <param name="contactEmail">The contact email of the user submitting the feedback.</param>
384+
/// <param name="name">The name of the user submitting the feedback.</param>
385+
/// <param name="replayId">The ID of the replay associated with the feedback.</param>
386+
/// <param name="url">The URL of the page or screen the feedback relates to.</param>
387+
/// <param name="associatedEventId">The ID of the event the feedback is associated with.</param>
388+
/// <param name="scope">The scope to apply to the feedback.</param>
389+
/// <param name="hint">An optional hint providing high-level context for the source of the event.</param>
390+
/// <returns>The Id of the captured feedback. Returns <see cref="SentryId.Empty"/> when capture failed.</returns>
346391
[DebuggerStepThrough]
347392
public static SentryId CaptureFeedback(string message, string? contactEmail = null, string? name = null,
348393
string? replayId = null, string? url = null, SentryId? associatedEventId = null, Scope? scope = null,

0 commit comments

Comments
 (0)