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
Start from ParameterSetName IshEventsGroup, same parameters like EventLevel, MetadataFilter, RequestedMetadata and of course IshSession
Just like -IshEvent is an array, so is -IshBackgroundTask ... if you do a group request you just get them concatenated as already implemented when offering multiple inputs on -IshEvent ... For IshEvent you go to _retrievedIshEvents , but for IshBackgroundTask you can immediately skip to progressRefs which we should rename to a class property _retrievedProgressRefs as they can already be filled up from the ProcessRecord function
Extend inline tripple-slash documentation for Get-Help usage
Add Pester test
/// <summary>
/// <para type="description">The <see cref="IshEvent"/>s that need to be handled.</para>
/// </summary>
[Parameter(Mandatory = true, ValueFromPipeline = true, ParameterSetName = "IshEventsGroup")]
public IshEvent[] IshEvent { get; set; }
The text was updated successfully, but these errors were encountered:
The request is to make it possible to easily catch and follow-up on the Events generated of a new BackgroundTask (see recent #193)
IshEventsGroup
, same parameters likeEventLevel
,MetadataFilter
,RequestedMetadata
and of courseIshSession
-IshEvent
is an array, so is-IshBackgroundTask
... if you do a group request you just get them concatenated as already implemented when offering multiple inputs on-IshEvent
... ForIshEvent
you go to_retrievedIshEvents
, but forIshBackgroundTask
you can immediately skip toprogressRefs
which we should rename to a class property_retrievedProgressRefs
as they can already be filled up from the ProcessRecord functionThe text was updated successfully, but these errors were encountered: