Add Delimiter parameter to Get-Clipboard#26134
Conversation
|
We could discuss a completer for better UX with values like Default (platform default), WindowsEndOfLine, UnixEndOfLine. |
|
@iSazonov I have added a delimiter completer. Where do we want to place these kinds of completers in the solution? Within the project that uses them? Or within the System.Management.Automation project under CommandCompletion? I noticed we already have a "ScopeArgumentCompleter" there but if we want to have a bunch of completer attributes then it might be worth creating a dedicated folder/namespace for that. |
Yes. It is good if we will decouple in-box modules in future. |
|
@MartinGC94 Please fix CodeFactor doc issue. |
|
/azp run PowerShell-Windows-Packaging-CI, PowerShell-CI-linux-packaging |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
📣 Hey @@MartinGC94, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗 https://aka.ms/PSRepoFeedback |
PR Summary
This PR adds a Delimiter parameter to Get-Clipboard allowing users to customize the delimiters used to split the content.
This was discussed in this issue: #25480
Note that I made the parameter a string array, rather than string. The reason for this is that it allows users to set a default value of
to handle both Windows and Linux line endings. If it was just a single string you'd have to be aware of the line endings before running the command.
PR Context
Fixes #25480
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright header-Delimiterparameter forGet-ClipboardMicrosoftDocs/PowerShell-Docs#12406