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
Copy file name to clipboardExpand all lines: README.md
+44-71Lines changed: 44 additions & 71 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -130,59 +130,33 @@ If the function relies on external or additional files, you will have to copy th
130
130
131
131
### [Get-PSProfile](docs/Get-PSProfile.md)
132
132
133
-
This command is designed for Windows systems and makes it easy to identify all possible PowerShell profile scripts. Including those for hosts such as VSCode or the PowerShell ISE. The command writes a custom object to the pipeline which has defined formatting. The default view is a table.
133
+
This command is designed to make it easy to identify all possible PowerShell profile scripts. Including those for hosts such as VSCode or the PowerShell ISE. The command writes a custom object to the pipeline which has defined formatting. The default view is a table.
Copy file name to clipboardExpand all lines: changelog.md
+28Lines changed: 28 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,34 @@
3
3
This file contains the most recent change history for the PSScriptTools module.
4
4
5
5
## [Unreleased]
6
+
### Added
7
+
- Added the parameter `NoComments` to `New-PSFormatXml` to suppress the default helper comments.
8
+
- Added a parameter alias `Property` for `Properties` in `New-PSFormatXML`.
9
+
- Added a parameter alias `Property` for `Properties` in `New-PSFormatXML`.
10
+
- Added alias `isAdmin` to `Test-IsElevated`.
11
+
12
+
### Changed
13
+
- Updated `Convert-CommandToHashTable` to better handle a hashtable as a paremeter value.
14
+
- Updated `ConvertTo-Hashtable` to using PSObject` to get property names.
15
+
- Updated `ConvertTo-Hashtable` to make an alphabetically sorted hashtable an ordered hashtable.
16
+
- Updated `Convert-HashtableToCode` to accept a standard or ordered hashtable as input.
17
+
- Revised `Get-MyVariable`. Removed the `-NoTypeInformation` and made it opt-in with -IncludeTypeInformation`. __This is a breaking change.__
18
+
- Revised `Get-MyVariable` to get initial variables from a new PowerShell instance.
19
+
- Revised `Get-MyAlias` to let user specify a name. The new version also skips aliases from common modules like PSReadline and Microsoft.PowerShell.PSResourceGet.
20
+
- Revised formatting for `Get-ModuleCommand` to add a link to online help for each command if running PowerShell 7.
21
+
- Updated `New-PSFormatXML` to incorporate a suggestion from [@scriptingstudio](https://github.com/scriptingstudio). [[Issue #155](https://github.com/jdhitsolutions/PSScriptTools/issues/155)]
22
+
- Updated `Get-PSProfile` to support non-Windows platforms. Reformatted the default table view.
23
+
- Updated `README`.
24
+
- Updated `Get-PSLocation` to include locations in `%PSModulePath%` Also corrected values for `HOME` and `Documents`. These changes also meant updating the custom formatting file..
25
+
- Updated `Get-PowerShellEngine` to define a type name (`PSEngine`) when writing a detailed object.
26
+
- Modified `Show-ANSISequence` to adjust number of columns to display in PowerShell 7.
27
+
- Code cleanup.
28
+
- Help updates.
29
+
- Replaced bit.ly online help links.
30
+
31
+
### Fixed
32
+
- Fixed bug in `Get-ModuleCommand` that failed to retrieve all command aliases.
33
+
- Fixed error in DirectoryStat sizeKB format view that wasn't showing values in KB
This command is intended to convert a long PowerShell expression with named parameters into a splatting alternative. The central concept is that you are editing a script file with a lengthy PowerShell expression with multiple parameters and you would like to turn it into splatting code.
22
+
This command is intended to convert a long PowerShell expression with named parameters into a splatting alternative. The central concept is that you are editing a script file with a lengthy PowerShell expression with multiple parameters and you would like to turn it into splatting code. For best results, the command expression should use parameter names and not rely on positional parameters.
23
+
24
+
The command may produce an invalid hashtable with complex expressions as parameter values.
The $text variable might be a line of code from your script. The second line converts into a splatting sequence and copies it to the Windows clipboard so you can paste it back into your script. You could create a VS Code task sequence using this function.
Use this command to convert a hashtable into its text or string equivalent. It is assumed that any array values contain items of the same type. This command has not been tested with large or complex hashtables, so you might need to manually edit the output to meet your tastes or requirements.
30
+
Use this command to convert a hashtable into its text or string equivalent. It is assumed that any array values contain items of the same type. This command has not been tested with large or complex hash tables, so you might need to manually edit the output to meet your requirements.
0 commit comments