Grammatical error:

[jbirley]

Chapter 7

Section: 7.1.2 Candidates for private functions

States

When deciding on if a PowerShell command should be public or private, we should answer the following questions:

Recommendation

When deciding if a PowerShell command should be public or private, we should answer the following questions:

Section: 7.1.2 Candidates for private functions

States

When looking at the AcmeEmployee, we can probably think of many functions that are good candidates to be private to the module.

Recommendation

When looking at the AcmeEmployee module, we can probably think of many functions that are good candidates to be private to the module.

Section: 7.1.3 Controlling the visibility of variables and aliases

States

15 # Define aliases
16 $aliases  = @()
17 $aliases += New-Alias -Name gae -Value Get-AcmeEmployee
18 $aliases += New-Alias -Name sae -Value Set-AcmeEmployee

Recommendation

15 # Define aliases
16 $aliases  = @()
17 $aliases += New-Alias -Name gae -Value Get-AcmeEmployee -PassThru
18 $aliases += New-Alias -Name sae -Value Set-AcmeEmployee -PassThru

Section: 7.2 Summary (Key points callout)

States

• Private functions are usually helper functions that whoever is consuming the module shouldn’t be concerned with.
• Just like with functions, we export local variables and aliases using Export-ModuleMember.

Recommendation

• Private functions are usually helper functions; whoever consumes the module shouldn’t be concerned with them.
• Just like functions, we export local variables and aliases using Export-ModuleMember.

[devblackops]

Thanks! Corrected.