The following page has a specific section for examples in PowerShell.
https://pnp.github.io/cli-microsoft365/cmd/adaptivecard/adaptivecard-send/#examples-for-powershell
These fragments do not work however.
In PowerShell, the double quotes should be escaped differently. For example:
m365 adaptivecard send --card "{ \`"someProperty\`": \`"Some value\`" }"Aside from this fact, I'd be in favor of doing this differently.
On every command that has complex JSON-content like this, we could remember the user to check how to escape values in various shells. We could point to a central page on our site where we explain that. We do not have those pages yet, so these should be created.
For now, we can at least remove these examples, as they are faulty anyway. Plus, we don't have these specific PowerShell examples anywhere else that we allow for JSON.
What do you think of this @pnp/cli-for-microsoft-365-maintainers ?
The following page has a specific section for examples in PowerShell.
https://pnp.github.io/cli-microsoft365/cmd/adaptivecard/adaptivecard-send/#examples-for-powershell
These fragments do not work however.
In PowerShell, the double quotes should be escaped differently. For example:
Aside from this fact, I'd be in favor of doing this differently.
On every command that has complex JSON-content like this, we could remember the user to check how to escape values in various shells. We could point to a central page on our site where we explain that. We do not have those pages yet, so these should be created.
For now, we can at least remove these examples, as they are faulty anyway. Plus, we don't have these specific PowerShell examples anywhere else that we allow for JSON.
What do you think of this @pnp/cli-for-microsoft-365-maintainers ?