Ironman Software Forums
Continue the conversion on the Ironman Software forums. Chat with over 1000 users about PowerShell, PowerShell Universal, and PowerShell Pro Tools.
This post outlines the new features of PowerShell Pro Tools and PowerShell Universal that have been added in the March 2023 release cycle.
PowerShell Universal now supports multiple API documentation definitions. You can assign endpoints to specific definitions and enforce authentication and authorization for each document. API documentation also supports defining custom PowerShell classes for input and output types for your endpoints.
As with all of our releases, we’ve released numerous components and parameters for existing components.
Define pages at dashboard startup and greatly increase the performance of pages that don’t change.
New-UDPage -Name 'Static!' -Content {
New-UDTypography (Get-Date)
} -Static
Separate sections of your dashboard with stylish dividers that support direction and icons.
New-UDDivider -Children {
New-UDIcon -Icon 'User'
}
Define sections of your dashboard using markdown with the New-UDMarkdown
cmdlet.
New-UDMarkdown -Markdown ' # Header
- List
- List 2
- [A link!](https://www.ironmansoftware.com)
'
Take advantage of the entire FontAwesome Pro icon set in your dashboards.
New-UDIcon -Icon 'FaceAwesome' -Size 5x -Color 'purple'
Allow your users to upload images to a published folder directly from a dashboard using New-UDEditor
.
In addition to other enhancements to the PowerShell Universal editor, you will now find PSScriptAnalyzer support. Analysis is run you type and warnings will be presented just as it would in Visual Studio Code.
The git history and sync status pages have been updated to better reflect the status of the PSU nodes and cluster. You will easily be able to see the sync status of nodes. Additionally, you will be able to view the entire git history for your repository directly in PowerShell Universal.
When taking advantage of manual git sync mode, you also have the ability to merge conflicting changes directly from the browser. You no longer need to leave PowerShell Universal to manage a merge conflict.
PSPackager now supports loading package.psd1
files that you will find in other tools within PowerShell Pro Tools. This allows the packager to use settings that are not available within the wizard.
PSScriptPad now integrates directly with the PSPackager. If you have PSPackager installed, clicking the Package icon in PSScriptPad will launch the wizard. If you have a package.psd1
file, it will be loaded automatically into the wizard.
Continue the conversion on the Ironman Software forums. Chat with over 1000 users about PowerShell, PowerShell Universal, and PowerShell Pro Tools.
Receive once-a-month updates about Ironman Software. You'll learn about our product updates and blogs related to PowerShell.