Tree: e75bc15953

master

4.2.6

4.2.4

4.2.3

5.0.0-rc9

5.0.0-rc8

5.0.0-rc7

5.0.0-rc6

5.0.0-rc5

5.0.0-rc4

5.0.0-rc3

5.0.0-rc2

5.0.0-rc1

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'e75bc15953'

${ noResults }

Commit Graph

1 Commits (e75bc15953989b4b3409a8c041b5306d258e70ab)

Author	SHA1	Message	Date
Raimund Andree	5486a9c9bc	docs(memory-bank): record Decision 26, the lessons of the piped AppliesTo, and the acceptance - Decision 26: Add and Remove for access and audit declare no default parameter set, what that changes for a piped object, and what stays silent (a value that PowerShell cannot convert to a scope is ignored and the object is handled as one without AppliesTo). - Debugging insights: a piped property selects a parameter set only when the cmdlet has no default set whose mandatory parameters the object satisfies; PowerShell resets only the parameters that the previous piped object bound, so a field that the cmdlet writes itself reaches the next object; probe the route that the documentation shows and each form of a value, not the one that you tried; a sentence about what a test proves is a claim too. - Active context and progress: the state after the fix, three independent reviews and two checks, the acceptance of the final package in the labs, and the open items; the remaining-path inventory is that of 2112ee3. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: AI Assistant <ai@example.com>	3 weeks ago