v0.3.0 public release

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,7 +1,7 @@
 name: Bug Report
 description: File a bug report
 labels: ["bug"]
-assignees:
+assignees: ["rebelinux"]
 body:
   - type: textarea
     id: bug-description

.github/ISSUE_TEMPLATE/change_request.yml

@@ -1,7 +1,7 @@
 name: Change Request
 description: Request a new change or an improvement
 labels: ["change request"]
-assignees:
+assignees: ["rebelinux"]
 body:
   - type: textarea
     id: description

.github/workflows/Release.yml

@@ -49,29 +49,30 @@ jobs:
               shell: pwsh
               run: |
                   Publish-Module -Path .\AsBuiltReport.Chart\ -NuGetApiKey ${{ secrets.PSGALLERY_API_KEY }} -Verbose
-    tweet:
-        needs: publish-to-psgallery
-        runs-on: ubuntu-latest
-        steps:
-            - uses: Eomm/why-don-t-you-tweet@v2
-              # We don't want to tweet if the repository is not a public one
-              if: ${{ !github.event.repository.private }}
-              with:
-                  # GitHub event payload
-                  # https://docs.github.com/en/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#release
-                  tweet-message: "[New Release] ${{ github.event.repository.name }} ${{ github.event.release.tag_name }}! Check out what's new! ${{ github.event.release.html_url }} #AsBuiltReport #PowerShell"
-              env:
-                  TWITTER_CONSUMER_API_KEY: ${{ secrets.TWITTER_CONSUMER_API_KEY }}
-                  TWITTER_CONSUMER_API_SECRET: ${{ secrets.TWITTER_CONSUMER_API_SECRET }}
-                  TWITTER_ACCESS_TOKEN: ${{ secrets.TWITTER_ACCESS_TOKEN }}
-                  TWITTER_ACCESS_TOKEN_SECRET: ${{ secrets.TWITTER_ACCESS_TOKEN_SECRET }}
-    bsky-post:
-        needs: publish-to-psgallery
-        runs-on: ubuntu-latest
-        steps:
-            - uses: zentered/bluesky-post-action@v0.3.0
-              with:
-                  post: "[New Release] ${{ github.event.repository.name }} ${{ github.event.release.tag_name }}! Check out what's new! ${{ github.event.release.html_url }} #AsBuiltReport #PowerShell"
-              env:
-                  BSKY_IDENTIFIER: ${{ secrets.BSKY_IDENTIFIER }}
-                  BSKY_PASSWORD: ${{ secrets.BSKY_PASSWORD }}
+    # tweet:
+    #     needs: publish-to-psgallery
+    #     runs-on: ubuntu-latest
+    #     steps:
+    #         - uses: Eomm/why-don-t-you-tweet@v2
+    #           # We don't want to tweet if the repository is not a public one
+    #           if: ${{ !github.event.repository.private }}
+    #           with:
+    #               # GitHub event payload
+    #               # https://docs.github.com/en/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#release
+    #               tweet-message: "[New Release] ${{ github.event.repository.name }} ${{ github.event.release.tag_name }}! Check out what's new! ${{ github.event.release.html_url }} #AsBuiltReport #PowerShell"
+    #           env:
+    #               TWITTER_CONSUMER_API_KEY: ${{ secrets.TWITTER_CONSUMER_API_KEY }}
+    #               TWITTER_CONSUMER_API_SECRET: ${{ secrets.TWITTER_CONSUMER_API_SECRET }}
+    #               TWITTER_ACCESS_TOKEN: ${{ secrets.TWITTER_ACCESS_TOKEN }}
+    #               TWITTER_ACCESS_TOKEN_SECRET: ${{ secrets.TWITTER_ACCESS_TOKEN_SECRET }}
+    # bsky-post:
+    #     needs: publish-to-psgallery
+    #     runs-on: ubuntu-latest
+    #     steps:
+    #         - uses: zentered/bluesky-post-action@v0.3.0
+    #           with:
+    #               post: "[New Release] ${{ github.event.repository.name }} ${{ github.event.release.tag_name }}! Check out what's new! ${{ github.event.release.html_url }} #AsBuiltReport #PowerShell"
+    #           env:
+    #               BSKY_IDENTIFIER: ${{ secrets.BSKY_IDENTIFIER }}
+    #               BSKY_PASSWORD: ${{ secrets.BSKY_PASSWORD }}
+

AsBuiltReport.Chart/AsBuiltReport.Chart.psd1

@@ -12,7 +12,7 @@
     RootModule = 'AsBuiltReport.Chart.psm1'
 
     # Version number of this module.
-    ModuleVersion = '0.2.0'
+    ModuleVersion = '0.3.0'
 
     # Supported PSEditions
     # CompatiblePSEditions = @()
@@ -69,7 +69,7 @@
     # NestedModules = @()
 
     # Functions to export from this module, for best performance, do not use wildcards and do not delete the entry, use an empty array if there are no functions to export.
-    FunctionsToExport = 'New-PieChart', 'New-BarChart', 'New-StackedBarChart'
+    FunctionsToExport = 'New-PieChart', 'New-BarChart', 'New-StackedBarChart', 'New-SignalChart'
 
     # Cmdlets to export from this module, for best performance, do not use wildcards and do not delete the entry, use an empty array if there are no cmdlets to export.
     # CmdletsToExport = '*'
@@ -127,3 +127,4 @@
 
 
 
+

AsBuiltReport.Chart/AsBuiltReport.Chart.psm1

@@ -5,15 +5,15 @@ switch ($PSVersionTable.PSEdition) {
             $architecture = [System.Runtime.InteropServices.RuntimeInformation]::OSArchitecture
             if ($architecture -eq "Arm64" -or $architecture -eq "Arm") {
                 Write-Verbose "Architecture: ARM (Apple Silicon)"
-                Import-Module ("$PSScriptRoot{0}Src{0}Assemblies{0}Core{0}mac-osx{0}osx-arm64{0}AsBuiltReportChart.dll" -f [System.IO.Path]::DirectorySeparatorChar) -Verbose -Debug
+                Import-Module ("$PSScriptRoot{0}Src{0}Assemblies{0}Core{0}mac-osx{0}osx-arm64{0}AsBuiltReportChart.dll" -f [System.IO.Path]::DirectorySeparatorChar)
 
             } elseif ($architecture -eq "X64" -or $architecture -eq "X86") {
                 Write-Verbose "Architecture: x86 (Intel)"
-                Import-Module ("$PSScriptRoot{0}Src{0}Assemblies{0}Core{0}mac-osx{0}osx-x64{0}AsBuiltReportChart.dll" -f [System.IO.Path]::DirectorySeparatorChar) -Verbose -Debug
+                Import-Module ("$PSScriptRoot{0}Src{0}Assemblies{0}Core{0}mac-osx{0}osx-x64{0}AsBuiltReportChart.dll" -f [System.IO.Path]::DirectorySeparatorChar)
 
             } else {
                 Write-Verbose "Architecture: Unknown or other architecture"
-                Import-Module ("$PSScriptRoot{0}Src{0}Assemblies{0}Core{0}mac-osx{0}osx-arm64{0}AsBuiltReportChart.dll" -f [System.IO.Path]::DirectorySeparatorChar)  -Verbose -Debug
+                Import-Module ("$PSScriptRoot{0}Src{0}Assemblies{0}Core{0}mac-osx{0}osx-arm64{0}AsBuiltReportChart.dll" -f [System.IO.Path]::DirectorySeparatorChar)
             }
         } elseif ($IsLinux) {
             Import-Module ("$PSScriptRoot{0}Src{0}Assemblies{0}Core{0}linux-x64{0}AsBuiltReportChart.dll" -f [System.IO.Path]::DirectorySeparatorChar)

CHANGELOG.md

@@ -5,6 +5,23 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.3.0] - 2026-03-14
+
+### Added
+
+- Add Signal chart support
+- Add support for setting the background color of the chart
+- Add documentation example on how to use the modules
+
+### Changed
+
+Update module version to 0.3.0
+
+### Fixed
+
+- Fix issue with the stacked chart not rendering correctly when using certain data sets
+- Fix pester test to properly validate the functionality of the module
+
 ## [0.2.0] - 2026-02-20
 
 ### Added
@@ -19,4 +36,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 
-- Initial release of AsBuiltReport Chart, providing basic charting capabilities for AsBuiltReport data visualization
+
+- Initial release of AsBuiltReport Chart, providing basic charting capabilities for AsBuiltReport data visualization
+
+

Examples/Example01.ps1

@@ -0,0 +1,61 @@
+<#
+    .SYNOPSIS
+    Example 01 - Basic Pie Chart
+
+    .DESCRIPTION
+    This example demonstrates how to create a basic Pie Chart using the AsBuiltReport.Chart module.
+    The chart displays a simple breakdown of VM power states across a vSphere environment.
+#>
+
+[CmdletBinding()]
+param (
+    [System.IO.DirectoryInfo] $Path = (Get-Location).Path,
+    [string] $Format = 'png'
+)
+
+<#
+    Starting with PowerShell v3, modules are auto-imported when needed. Importing the module here
+    ensures clarity and avoids ambiguity.
+#>
+
+# Import-Module AsBuiltReport.Chart -Force -Verbose:$false
+
+<#
+    Since the chart output is a file, specify the output folder path using $OutputFolderPath.
+#>
+
+$OutputFolderPath = Resolve-Path $Path
+
+<#
+    Define the data to be displayed in the chart.
+    In a real-world scenario these values would come from your infrastructure query.
+#>
+
+$ChartTitle  = 'VM Power States'
+$Values      = @(120, 35, 10)
+$Labels      = @('Powered On', 'Powered Off', 'Suspended')
+
+<#
+    The New-PieChart cmdlet generates the Pie Chart image.
+
+    -Title              : Sets the chart title displayed at the top of the image.
+    -Values             : Array of numeric values, one per slice.
+    -Labels             : Array of label strings corresponding to each value.
+    -Format             : Output file format (e.g. png, jpg, svg).
+    -OutputFolderPath   : Directory where the generated chart file will be saved.
+    -Width              : Width of the chart image in pixels.
+    -Height             : Height of the chart image in pixels.
+    -ColorPalette       : Predefined color palette (e.g. Category20, Pastel).
+    -Filename           : Name of the output file (without extension).
+#>
+
+New-PieChart `
+    -Title $ChartTitle `
+    -Values $Values `
+    -Labels $Labels `
+    -Format $Format `
+    -OutputFolderPath $OutputFolderPath `
+    -Width 600 `
+    -Height 400 `
+    -ColorPalette Category20 `
+    -Filename 'Example01-PieChart'

Examples/Example02.ps1

@@ -0,0 +1,98 @@
+<#
+    .SYNOPSIS
+    Example 02 - Pie Chart with Legend, Custom Colors and Border
+
+    .DESCRIPTION
+    This example demonstrates how to create a Pie Chart with additional visual options, including:
+    - An enabled legend with custom alignment and orientation
+    - A custom hex color palette
+    - A chart border
+    - Adjusted title and label font sizes
+    - Custom chart dimensions
+
+    The chart displays a server operating system distribution report.
+#>
+
+[CmdletBinding()]
+param (
+    [System.IO.DirectoryInfo] $Path = (Get-Location).Path,
+    [string] $Format = 'png'
+)
+
+<#
+    Starting with PowerShell v3, modules are auto-imported when needed. Importing the module here
+    ensures clarity and avoids ambiguity.
+#>
+
+# Import-Module AsBuiltReport.Chart -Force -Verbose:$false
+
+<#
+    Since the chart output is a file, specify the output folder path using $OutputFolderPath.
+#>
+
+$OutputFolderPath = Resolve-Path $Path
+
+<#
+    Define the data to be displayed in the chart.
+    In a real-world scenario these values would come from your infrastructure query.
+#>
+
+$ChartTitle  = 'Server OS Distribution'
+$Values      = @(85, 60, 30, 15)
+$Labels      = @('Windows Server 2022', 'Windows Server 2019', 'RHEL 9', 'Ubuntu 22.04')
+
+<#
+    A custom hex color palette can be used to match corporate branding or improve readability.
+    Each color corresponds to a slice in the order they appear in $Values.
+#>
+
+$CustomColors = @('#0078D4', '#00B7C3', '#E74C3C', '#F39C12')
+
+<#
+    The New-PieChart cmdlet generates the Pie Chart image.
+
+    -Title                    : Sets the chart title.
+    -TitleFontSize            : Sets the font size of the title in points.
+    -TitleFontBold            : Renders the title in bold.
+    -Values                   : Array of numeric values, one per slice.
+    -Labels                   : Array of label strings corresponding to each value.
+    -LabelFontSize            : Sets the font size of the slice labels.
+    -LabelDistance            : Controls how far labels are placed from the chart center (0.5-0.9).
+    -EnableLegend             : Enables the legend on the chart.
+    -LegendAlignment          : Positions the legend (e.g. UpperRight, LowerCenter).
+    -LegendOrientation        : Sets legend layout direction (Vertical or Horizontal).
+    -LegendFontSize           : Sets the legend text font size in points.
+    -EnableChartBorder        : Draws a border around the chart area.
+    -ChartBorderColor         : Sets the border color.
+    -ChartBorderSize          : Sets the border thickness in pixels.
+    -EnableCustomColorPalette : Enables use of the custom color palette.
+    -CustomColorPalette       : Array of hex color strings for each slice.
+    -Width                    : Output image width in pixels.
+    -Height                   : Output image height in pixels.
+    -Format                   : Output file format (e.g. png, jpg, svg).
+    -OutputFolderPath         : Directory where the generated chart file will be saved.
+    -Filename                 : Name of the output file (without extension).
+#>
+
+New-PieChart `
+    -Title $ChartTitle `
+    -TitleFontSize 18 `
+    -TitleFontBold `
+    -Values $Values `
+    -Labels $Labels `
+    -LabelFontSize 13 `
+    -LabelDistance 0.7 `
+    -EnableLegend `
+    -LegendAlignment UpperRight `
+    -LegendOrientation Vertical `
+    -LegendFontSize 12 `
+    -EnableChartBorder `
+    -ChartBorderColor Black `
+    -ChartBorderSize 2 `
+    -EnableCustomColorPalette `
+    -CustomColorPalette $CustomColors `
+    -Width 600 `
+    -Height 400 `
+    -Format $Format `
+    -OutputFolderPath $OutputFolderPath `
+    -Filename 'Example02-PieChart-Advanced'

Examples/Example03.ps1

@@ -0,0 +1,61 @@
+<#
+    .SYNOPSIS
+    Example 03 - Basic Bar Chart
+
+    .DESCRIPTION
+    This example demonstrates how to create a basic Bar Chart using the AsBuiltReport.Chart module.
+    The chart displays CPU utilization across a set of ESXi hosts.
+#>
+
+[CmdletBinding()]
+param (
+    [System.IO.FileInfo] $Path = (Get-Location).Path,
+    [string] $Format = 'png'
+)
+
+<#
+    Starting with PowerShell v3, modules are auto-imported when needed. Importing the module here
+    ensures clarity and avoids ambiguity.
+#>
+
+# Import-Module AsBuiltReport.Chart -Force -Verbose:$false
+
+<#
+    Since the chart output is a file, specify the output folder path using $OutputFolderPath.
+#>
+
+$OutputFolderPath = Resolve-Path $Path
+
+<#
+    Define the data to be displayed in the chart.
+    In a real-world scenario these values would come from your infrastructure query.
+#>
+
+$ChartTitle  = 'ESXi Host CPU Utilization (%)'
+$Values      = @(72, 45, 88, 61, 53)
+$Labels      = @('esxi-host-01', 'esxi-host-02', 'esxi-host-03', 'esxi-host-04', 'esxi-host-05')
+
+<#
+    The New-BarChart cmdlet generates the Bar Chart image.
+
+    -Title              : Sets the chart title displayed at the top of the image.
+    -Values             : Array of numeric values, one per bar.
+    -Labels             : Array of label strings corresponding to each bar.
+    -LabelXAxis         : Label for the X-axis.
+    -LabelYAxis         : Label for the Y-axis.
+    -Format             : Output file format (e.g. png, jpg, svg).
+    -OutputFolderPath   : Directory where the generated chart file will be saved.
+    -Filename           : Name of the output file (without extension).
+#>
+
+New-BarChart `
+    -Title $ChartTitle `
+    -Values $Values `
+    -Labels $Labels `
+    -LabelXAxis 'Host' `
+    -LabelYAxis 'CPU (%)' `
+    -Format $Format `
+    -OutputFolderPath $OutputFolderPath `
+    -Width 600 `
+    -Height 600 `
+    -Filename 'Example03-BarChart'