#use the file from this module

$mapData = [System.Collections.Generic.List[object]]::new()

Get-Content -path $map | ConvertFrom-Json | Foreach-Object {$_} | foreach-Object {

$entry = [pscustomobject]@{

PSTypeName = "PSAnsiFileEntry"

Description = $_.description

Pattern = $_.pattern

Ansi = $_.ansi

}

$mapData.Add($entry)

}

Set-Variable -Name PSAnsiFileMap -value $mapdata -Scope Global

+ [ANSI Tools](#Ansi-Tools)

This module includes several custom format files for common objects like services. You can run `Get-Service` and pipe it to the custom table view.

The map includes ANSI settings for different file types. You won't see the ANSI value in the output. The module will add a custom table view called `ansi` which you can use to display colorized file results.

The mapping file is user-customizable. Copy the `psansifilemap.json` file from the module's root directory to $HOME. When you import this module, if the file is found, it will be imported and used as `psansifilemap`, otherwise, the module's file will be used.

You can create or modify file groups. The Pattern value should be a regular expression pattern to match the filename. Don't forget you will need to escape characters for the JSON format. The Ansi value will be an ANSI escape sequence. You can use `\u001b` for the \``e` character.

If you prefer not to edit JSON files, you can use the PSAnsiFileMap commands from the module.

This command will display the value of the `$PSAnsiFileMap` variable, but will also show the ANSI sequence using the sequence itself.


Use this command to modify an existing entry. You need to specify a regular expression pattern to match on the filename and/or an ANSI escape sequence. If the entry description doesn't exist, you will need to specify the regex pattern and the ANSI sequence to add the entry to $PSAnsiFileMap.

If you need to, you can remove an entry from `$PSAnsiFileMap`.

Any changes you make to `$PSAnsiFileMap` will only last until you import the module again. To make the change permanent, use [Export-PSAnsiFileMap](docs/Export-PSAnsiFileMap.md). This will create the `psansifilemap.json` file in your `$HOME` directory. When you import the PSSCriptTools module, if this file is found, it will be imported. Otherwise, the default module file will be used.

From time to time I will include additional items that you might find useful in your PowerShell work.

Last Updated *2020-12-28 18:38:04Z*

This is the most recent change history for this module.

+ Fixed typo bug in `Get-PSScriptTools` that was failing to get command aliases. (Issue #99)

+ Modified `Get-PSScriptTools` to improve performance. Assuming that all exported functions use standard verbs.

+ Added `Get-PSAnsiFileMap`.

+ Added `Set-PSAnsiFileMapEntry`.

+ Added `Remove-PSAnsiFileMapEntry`.

+ Added `Export-PSAnsiFileMap`.

+ Added `Show-ANSISequence`.

+ Updated `filesystem.ansi.format.ps1xml` to use last matching pattern.

+ Modified `Show-Tree` to better handle piped-in file and directory objects.

+ Added an alias `ab` for `Add-Border`.

+ Added an alias of `nab` for `New-AnsiBar`.

+ Updated `README.md`.

+ Help updates.

This command will create a character or text-based border around a line of text. You might use this to create a formatted text report or to improve the display of information to the screen.

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.