Releases: dsccommunity/DscResource.Common
Releases · dsccommunity/DscResource.Common
v0.19.1-preview0001
[v0.19.1-preview0001]
Added
- Added Indented.AnalyzerRules and config
- Use prerelease DscResource.ScriptAnalyzer
Changed
- Move docs generation to separate task.
- Remove build.yml config not required.
Fixed
- Fixed HQRM scriptanalyzer errors
v0.19.0
v0.19.0-preview0001
[v0.19.0-preview0001]
Changed
- Unit Tests
- Updated path to
build.ps1
in BeforeDiscovery block.
- Updated path to
Assert-Module
- Added
SkipEditionCheck
for PS6+. Fixes #131.
- Added
v0.18.0
v0.18.0-preview0002
[v0.18.0-preview0002]
v0.18.0-preview0001
[v0.18.0-preview0001]
v0.17.3-preview0001
[v0.17.3-preview0001]
v0.17.2
[v0.17.2]
Added
- Public command:
Get-UserName
- get current user name cross platform.
Fixed
Get-PSModulePath
- Throws an exception if the My Documents folder cannot be found when
calling the command with the scopeCurrentUser
(issue #122).
- Throws an exception if the My Documents folder cannot be found when
v0.17.2-preview0001
[v0.17.2-preview0001]
Added
- Public command:
Get-UserName
- get current user name cross platform.
Fixed
Get-PSModulePath
- Throws an exception if the My Documents folder cannot be found when
calling the command with the scopeCurrentUser
(issue #122).
- Throws an exception if the My Documents folder cannot be found when
v0.17.1
[v0.17.1]
Added
Get-PSModulePath
- Can now return the individual module path for different scopes when
using the parameter-Scope
. If no parameter is specified the command
return the path for the scope CurrentUser.
- Can now return the individual module path for different scopes when
Test-ModuleExist
- Checks if a PowerShell module with a specified name is available in a
PSModulePath.
- Checks if a PowerShell module with a specified name is available in a
Fixed
Get-PSModulePath
- Was using the wrong path separator on Linux and macOS.
Get-LocalizedData
- Wrongly returned one or more boolean values in addition to
the localized string array. This was becuase the return value
was not handled when callingAdd()
andRemove()
methods of
$PSBoundParameters
so it was returned to the pipeline.
- Wrongly returned one or more boolean values in addition to