Description
https://api.github.com/repos/StartAutomating/PipeScript/issues
is a valid PowerShell command.
PipeScript should be able to transpile this into:
Invoke-RestMethod 'https://api.github.com/repos/StartAutomating/PipeScript/issues'
Of course, why stop there?
If one looks at this from a framework perspective, it makes sense to treat https:// as just one of a number of transpilers.
This opens the door to any protocol being abstracted away in PipeScript.
Additionally, command names can contain what appear to be variables:
$Owner = 'StartAutomating'
$repo = 'PipeScript'
https://api.github.com/repos/$Owner/$Repo/issues # This is a valid command, but the variables would not be replaced.
To add to the bonus points, this form would allow an arbitrary parameters (to be passed to whatever protocol transpiler or underlying command):
https://api.github.com/repos/StartAutomating/PipeScript/issues -Invoker Invoke-GitHubRestAPI
And, to add one more layer to the potential value, another module could have a protocol transpiler that supercedes the Rank, thus making and example like the one below capable of having its own invoker.
https://mydomain.com/