Skip to content

Conversation

@michaelblyons
Copy link
Collaborator

@michaelblyons michaelblyons commented Dec 8, 2025

Depends on #202. Big potential for annoying behavior, but maybe the upside is worth it.

I'm hesitant to make quoted strings into commands, but that might be the right move. In theory, you're supposed to run Invoke-Command on a string to execute it, but the M$ docs also have a workflow example containing:

foreach ($h in $Hotfix) {'D:\Scripts\Verify-Hotfix' -Hotfix $h}

And I ask: How do you know that the string is for executing? (Edit: Apparently workflows are invalid in Pwsh 6+)

In the meantime, I have decided that following the & or . operators should qualify a string as a command.

@michaelblyons michaelblyons mentioned this pull request Dec 8, 2025
21 tasks
@michaelblyons
Copy link
Collaborator Author

@msftrncs Hey Carl, do you have test assertions laying around from your previous work on the VSC/Atom tmLanguage for PowerShell? I could use some of the medium-to-gnarly test cases to see how I'm doing with Sublime Text's hard fork.

@michaelblyons michaelblyons force-pushed the command-freeform branch 2 times, most recently from d0d5498 to 9d0d77b Compare December 9, 2025 02:36
following regex operators
@michaelblyons
Copy link
Collaborator Author

I'm merging into #202. See you folks there!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rebuild syntax not to rely on "Approved Verbs"

1 participant