For generic PowerShell questions you can use the community slack http://slack.poshcode.org/
No. I'm calling them. They have parameters like
--playlist-start and --playlist-end.
@Aprazeth: They do have a --playlist-items. It's described as shown below:
Playlist video items to download. Specify indices of the videos in the playlist separated by commas like:
--playlist-items 1,2,5,8if you want to download videos indexed 1, 2, 5, 8 in the playlist. You can specify range:--playlist-items 1-3,7,10-13, it will download the videos at index 1, 2, 3, 7, 10, 11, 12 and 13.
However, I'm not using that option as of now.
When my script is called, I translate each parameter into the perl program's counterpart.
But since a start should always be less than a end, I'm trying to ensure that if both are specified, the start is less than the end.
Had a few things to do here - hence
I'm writing a PowerShell module with C#. How do I detect that an optional parameter wasn't specified. Can I access
$PSBoundParameters? Do I put ? on the parameter type? In this case, the optional parameter is an enum.
Also, there is a community discord for PowerShell at https://aka.ms/psdiscord - which might be a lot more active
@Aprazeth: I needed to derive from PSCmdLet rather than CmdLet. That provides access to the MyInvocations member which has BoundParameters.
wait why isn't it in #bridge on Discord
I was reading how yt-dlp has manpages available. That got me wondering if Powershell supports them or anything similar for components that don't directly support Powershell. We're talking about programs that come as EXE files.
It also would be nice if EXE files could provide auto-complete information for their command line options. Note that with many programs ported from *nix,
-axi is equivalent to -a -x -i. That would be an obstacle.
Then would PowerShell need to know when to translate
-x into /x for older DOS programs.
I would suggest having a field in the auto-complete information file describing which is needed. You then default it one way or the other so it can be anticipated what to do if the file omits that field.
As for the previously mentioned MAN documentation, that supports something that Powershell's system doesn't: Color.
I've been going through Create a Crescendo cmdlet - PowerShell | Microsoft Docs. Unfortunately, there's a problem with the samples is that a parameter might be optional in one parameter set, but mandatory in another.
In my case, I'm working on a cmdlet where several parameters can be specified, but you must specify at least one.
No mention is made of the Position option for the
ParameterAttribute.
Also, can a parameter be one of several types? For instance, if the parameter is a URL, I like to accept either a
System.URI or a string. For a folder, I like to take either a System.IO.Directory or a string.
4 replies
Hi guys, I raised a feature request issue ~2 years ago, and the thread is pretty dead. I've just realised that the issue doesn't have a "Needs Triage" label, and I can't see any way to add the label myself.
Is there anyone here who can add labels to issues?
PowerShell/PowerShell#12047
Is there anyone here who can add labels to issues?
PowerShell/PowerShell#12047
Weird. On Windows 11 Pro, PowerShell 7.2.4 thinks it's running on Windows 10.0.22000.
If I'm expecting a
System.Guid, I don't want them passing 4. Plus, this way, I'm not converting objects to/and from string as much.
Crescendo needs a documentation site for the schema. It should provide details on each field and samples. For instance, a page should be present describing the
HandlerType and Handler members of a OutputHandler member. What do those values mean? A few random blog posts don't count. It would appear that HandlerType can only have one of several values. So list them and describe each. Then describe how that affects how Handler is interpreted.
1 reply
Doesn't look like it.
If I have a string with an unknown number of whitespace characters at the start, is there a handy way to determine how many?
Well, I wrote a class method:
hidden [int]GetIndentLevel()
{
$this.CurLine -match '^(?<Indent>\s*';
return $Matches.Indent -split '( |\t)';
}
Are PowerShell classes passed by reference? I'm looking for the equivilent of the C#
ref keyword so I can have a function I call make changes to a variable in my scope.
I see
[ref], but that's a type by itself and ruins my type safety. I'd rather declare the parameter as ref [int] name and pass the variable with ref valueVar like I would with C#.
The documentation for
[ref] also seems to suggest it's mainly for COM.
People still explicitly use COM?
So 1990s.
Well, based on this, that's a resounding no.
C:\Users\willp> function Test([string]$x){$x = '%'}
C:\Users\willp> $g = 'dgfd'
C:\Users\willp> Test($g)
C:\Users\willp> $g
dgfd
C:\Users\willp> function Test([ref]$x){$x = '%'}
C:\Users\willp> Test($g)
Test: Cannot process argument transformation on parameter 'x'. Reference type is expected in argument.
Neither option worked.
Well, I had the usage of
[ref] wrong, but I'm still missing something.C:\Users\willp> Test(([ref]$g))
C:\Users\willp> $g
dgfd
C:\Users\willp> function Test([string]$x){$x = '%'}
C:\Users\willp> Test(([ref]$g))
C:\Users\willp> $g
dgfd
I got it working, but I don't like the lack of type safety. I don't know why my C# PowerShell module won't load, but if I can figure it out, I'm scrapping this script and starting over in C#.
Probably would result in faster code.