You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/// An optional callback/action which exposes the various <see cref="IHasPerformanceEvents"/> which may be subscribed-to in order to be notified
97
+
/// A collection of optional callbacks/actions which expose the various <see cref="IHasPerformanceEvents"/> which may be subscribed-to in order to be notified
98
98
/// of the progress of a screenplay.
99
99
/// </summary>
100
100
/// <remarks>
@@ -104,12 +104,18 @@ public sealed class ScreenplayOptions
104
104
/// If you wish, you may subscribe to these events from your own logic in order to develop new functionality or extend Screenplay.
105
105
/// </para>
106
106
/// <para>
107
-
/// There is no need to add an explicit subscription to any events for the reporting infrastructure.
108
-
/// Screenplay will automatically subscribe to this object from the reporting mechanism, unless the value of <see cref="ReportPath"/> means that
109
-
/// reporting is disabled.
107
+
/// There is no need to use this mechanism in order to use the Screenplay Reporting infrastructure.
108
+
/// Built-in logic will automatically subscribe to the event published from the reporting infrastructure.
109
+
/// Note that if <see cref="ReportPath"/> is a null or whitepsace-only string, the reporting infrastructure will be disabled.
110
+
/// </para>
111
+
/// <para>
112
+
/// This collection of configuration callbacks may be used to subscribe to the event publisher from custom Screenplay extensions, in order
113
+
/// be notified at particular points in the Screenplay's lifecycle.
114
+
/// Each extension should add a single item to this list of callbacks. In this manner, multiple extensions may coexist without worrying about
115
+
/// overwriting one another's event subscriptions.
0 commit comments