Damien Solodow
Damien Solodow
I'm seeing this as well but only on the beta endpoint. 1.11.1 shows the filter param on the beta endpoint though
What I'd be inclined to do is modify the test scripts so that the environment specific hard codes are variables at the top of the file(s), and then before the...
I only encountered it with that specific module version. I updated to a newer module, and re-ran from the clean ISO and it was good.
Let me make sure I'm reading the docs correct to do this: - create script with save-module and save the script in OSDBuilder\Content\Scripts - put script name in "Scripts" in...
I looked at that doc, and I may be missing something but it doesn't seem to prevent the integrated console from displaying the BOM character?
It _looks like_ the issue is with utils.cs lines 985-990. If I read it correctly, it's looking at host.version and saying "if greater than 6.0, PowerShell, if less than, Windows...
The linked issue had a note that linked to what PowerShellEditorServices does (if that helps): https://github.com/PowerShell/PowerShellEditorServices/blob/main/src/PowerShellEditorServices/Utility/VersionUtils.cs
no luck with a fix on this yet?