Justin Grote
Justin Grote
Thanks! Debugging remote runspaces can be inherently finicky because we have to do some ugly stuff to fetch the call stack and whatnot and it's hard to have good test...
Thanks for your submission! This is a [ScriptAnalyzer ](https://github.com/PowerShell/PSScriptAnalyzer) issue. Please file an issue there with this reproduction, and report back if it gets fixed there. I'll leave this issue...
Great! I'm actually going to leave this open until the newest version gets bundled into the extension. Assigning @andyleejordan to coordinate.
Thanks for the submission! This may be doable, the tricky part is identifying a PowerShell file path in all potential contexts, and supporting both Linux and Windows paths. I don't...
I've only ever seen it in the logs, doing simple pattern matching.
@JensGJ everything seems simple till you get down to the nitty gritty of it :) For instance, what about this: `. $PSScriptRoot/$(myfilepath)` where $(myfilepath) is not specified in the scope....
Related: https://github.com/microsoft/vscode/issues/108527
I don't think it should be a separate cmdlet but `-DestinationPath` should be part of a separate parameterset. Unfortunately that would be abreaking change now for anyone already expecting it...
Good catch! That's definitely an enhancement that needs to be made.
It appears I too erroneously thought that this "schema" was a [JSON schema](https://json-schema.org/) and not just a JSON that defines a schema. Can someone assist me for where this "format"...