Skip to content

Conversation

@michaeltlombardi
Copy link
Contributor

@michaeltlombardi michaeltlombardi commented Sep 5, 2023

PR Summary

Prior to this change, the Path parameter for the Convert-Path cmdlet indicated that it does not accept wildcard values, even though it does.

This change:

PR Checklist

  • Descriptive Title: This PR's title is a synopsis of the changes it proposes.
  • Summary: This PR's summary describes the scope and intent of the change.
  • Contributor's Guide: I have read the contributors guide.
  • Style: This PR adheres to the style guide.

…Path`

Prior to this change, the **Path** parameter for the `Convert-Path` cmdlet
indicated that it does not accept wildcard values, even though it does.

This change:

- Updates the metadata to accurately reflect the cmdlet behavior
- Fixes AB#156610
- Resolves MicrosoftDocs#10385
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit eec6c98:

✅ Validation status: passed

File Status Preview URL Details
reference/5.1/Microsoft.PowerShell.Management/Convert-Path.md ✅Succeeded View (powershell-5.1)
reference/7.2/Microsoft.PowerShell.Management/Convert-Path.md ✅Succeeded View (powershell-7.2)
reference/7.3/Microsoft.PowerShell.Management/Convert-Path.md ✅Succeeded View (powershell-7.3)
reference/7.4/Microsoft.PowerShell.Management/Convert-Path.md ✅Succeeded View (powershell-7.4)

For more details, please refer to the build report.

For any questions, please:

@michaeltlombardi michaeltlombardi merged commit 54744e9 into MicrosoftDocs:main Sep 5, 2023
@michaeltlombardi michaeltlombardi deleted the ab-156610/main/convert-path-wildcards branch September 13, 2023 20:09
@JamesDBartlett3
Copy link
Contributor

@michaeltlombardi, I was perusing the latest commits, and I could not help noticing all of the places where two-word phrases were replaced with one-word contractions (e.g. they are replaced with they're, it is replaced with it's, etc.). Contractions are generally considered inappropriate in formal writing, but I am not sure whether technical documentation is considered "formal writing" or not, so that particular concern may not apply here. This is mostly a matter of curiosity on my part, so please do not take offense; I am just wondering: Were these changes made in accordance with a style guide, or perhaps made automatically by a quirky English grammar linter of some kind?

@sdwheeler
Copy link
Collaborator

@michaeltlombardi, I was perusing the latest commits, and I could not help noticing all of the places where two-word phrases were replaced with one-word contractions

See https://learn.microsoft.com/en-us/style-guide/word-choice/use-contractions

@JamesDBartlett3
Copy link
Contributor

Ah, I figured it was probably deliberate. This is good to know! Thanks for pointing me in the right direction, @sdwheeler. 😊

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.

the -Path parameter for Convert-Path does support wildcards

3 participants