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
Added Func<T> generic annotation accesssor
Moved value annotation accessor to own file
Removed Try<specific thing> from ValueSubsystem to encourage <annotationId>.<specific thing>.Get/Set
Cleanup, took some analyzer suggestions
XML Docs improved
/// Associates an annotation with a <see cref="CliSymbol"/>. The symbol must be an option or argument and the value must be of the same type as the symbol./>.
10
+
/// </summary>
11
+
/// <remarks>
12
+
/// The annotation will be stored by the accessor's owner <see cref="CliSubsystem"/>.
13
+
/// </remarks>
14
+
/// <typeparam name="TValue">The type of value to be stored</typeparam>
15
+
/// <param name="owner">The subsystem that this annotation store data for.</param>
16
+
/// <param name="id">The identifier for this annotation, since subsystems may have multiple annotations.</param>
/// Associates an annotation with a <see cref="CliSymbol"/>. The symbol must be an option or argument and the delegate must return a value of the same type as the symbol./>.
10
+
/// </summary>
11
+
/// <remarks>
12
+
/// The annotation will be stored by the accessor's owner <see cref="CliSubsystem"/>.
13
+
/// </remarks>
14
+
/// <typeparam name="TValue">The type of value to be stored</typeparam>
15
+
/// <param name="owner">The subsystem that this annotation store data for.</param>
16
+
/// <param name="id">The identifier for this annotation, since subsystems may have multiple annotations.</param>
/// Executes the behavior of the subsystem. For example, help would write information to the console.
76
108
/// </summary>
77
109
/// <param name="pipelineContext">The context contains data like the ParseResult, and allows setting of values like whether execution was handled and the CLI should terminate </param>
78
110
/// <returns>A CliExit object with information such as whether the CLI should terminate</returns>
// @mhutch: Is the TryGet on the sparse dictionaries how we should handle a case where the annotations will be sparse to support lazy? If so, should we have another method on
13
-
// the annotation wrapper, or an alternative struct when there a TryGet makes sense? This API needs review, maybe next Tuesday.
0 commit comments