Autoformat cmdlet (and parameters) capitalization
See original GitHub issueSummary of the new feature
Document formatter should be able to convert default cmdlets (and it’s parameters) case, when some setting is set. (powershell.codeFormatting.keepcmdletcapitalization
)
Before formatting:
get-content "somefile.json" -raw | convertfrom-json
After formatting:
Get-Content "somefile.json" -Raw | ConvertFrom-Json
Issue Analytics
- State:
- Created 5 years ago
- Comments:6
Top Results From Across the Web
Code Layout and Formatting - PowerShell Practice and Style
A special case is made for two-letter acronyms in which both letters are capitalized, as in the variable $PSBoundParameters or the command Get-PSDrive...
Read more >Strongly Encouraged Development Guidelines - PowerShell
Use Pascal case for parameter names. In other words, capitalize the first letter of verb and all terms used in the noun.
Read more >Manage SQL code formatting using SQL formatter options
In the Capitalization tab can be set a various capitalization rule for the SQL keywords, Data types, Identifiers, System functions, ...
Read more >MS Word: configure options with PowerShell
Of course, you'll want to change the $true and $false values according to your ... correctTableCells = $false # Capitalize first letter of...
Read more >Basic Editing in Visual Studio Code
The modifiers can also be stacked - for example, \u\u\u$1 will uppercase the ... There are two arguments that you can pass to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Ash258 This is the distributed-federated model of git-managed, open-source software. It’s the dominant model now because it supports separation of concerns and code reuse. But it also means our workflow is exposed.
At this point you are dealing with the implementation, not an abstraction. You’re probably going to have to learn how the sausage is made to some extent.
This issue is helpful because it means you don’t need to read our codebase – we can help direct you to the right place. This is also the standard in the .NET Core and VSCode repos.
Since you understand the feature you are asking for, you are the best person to own the issue in PSScriptAnalyzer – otherwise there is a risk that something else will be implemented.
We’ll track the feature request here too though, since (1) it will help others with the same request, and (2) it can track any integration work we need to do.
@rkeithhill Shouldn’t this be done by collaborators?? I dont use PSScriptanalyzer, I don’t know anything about how this repository integrates it. If i would report it to PSScriptAnalyzer, they could want to know some technically information, which i dont’t know.
I am just using this extension and want it to be able to propose me this option. How it is implemented is on collaborators of this repo.