The property `$PSStyle.AutoSizeDefaultFormatting` is added to allow user to force the default implicit formatting to use `AutoSize` for Table and Wide views
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- powershell
- Domain
- documentation
Research direction
Start by reviewing related source pull request #28018 to understand the new $PSStyle.AutoSizeDefaultFormatting property and its interaction with OutputRendering. Update the PowerShell documentation to explain the property and its purpose, with the documented usage showing how it reduces formatted output verbosity.
Written by the indexing model from the issue text.
Description
Prerequisites
- Existing Issue: Search the existing issues for this repository. If there is an issue that fits your needs do not file a new one. Subscribe, react, or comment on that issue instead.
- Descriptive Title: Write the title for this issue as a short synopsis. If possible, provide context. For example, "Document new
Get-Foocmdlet" instead of "New cmdlet."
Summary
https://github.com/PowerShell/PowerShell/pull/28018 added a new property $PSStyle.AutoSizeDefaultFormatting to allow user to force the default implicit formatting to use AutoSize for Table and Wide views.
This is for reducing output verbosity when PowerShell is used by an agent. By setting the following 2 PSStyle properties, no color ANSI sequences will be written out and the tab formatting will take less spaces.
$PSStyle.AutoSizeDefaultFormatting = $true
$PSStyle.OutputRendering = 'PlainText'
Details
No response
Articles
No response
Related Source Pull Requests
Related Source Issues
No source issues. This is part of the effort to reduce token consumption by PowerShell when used as the shell invocation tool.
- Dominant language
- PowerShell
- Stars
- 2.5k
- Forks
- 1.7k
- Avg merge
- 8h 45m
- Merged PRs (30d)
- 33
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MicrosoftDocs/PowerShell-Docs
-
hold-for-pr hold-for-release issue-doc-idea
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MicrosoftDocs/PowerShell-Docs#13195 ·
-
hold-for-pr hold-for-release
Difficulty 1/5 Under an hour Newbie friendliness 88/100
MicrosoftDocs/PowerShell-Docs#12897 ·
-
Add "Avoid function / scriptblock based recursion" section to `Performance Considerations` document Openarea-sdk-docs
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MicrosoftDocs/PowerShell-Docs#11037 · 1 reaction ·
-
hold-for-pr hold-for-release
Difficulty 4/5 3-5 days Newbie friendliness 48/100
MicrosoftDocs/PowerShell-Docs#13172 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
MicrosoftDocs/PowerShell-Docs#12948 · 2 reactions ·
All issues in MicrosoftDocs/PowerShell-Docs
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·