Fixes #11606 - Add information about numeric parameter names

[sdwheeler]

PR Summary

Add information about numeric parameter names

• Fixes AB#359338
• Fixes Add warning to avoid naming a parameter beginning with a number #11606

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.

[learn-build-service-prod]

Learn Build status updates of commit 73dad68:

✅ Validation status: passed

File	Status	Preview URL	Details
reference/5.1/Microsoft.PowerShell.Core/About/about_Functions_Advanced_Parameters.md	✅Succeeded	View (powershell-5.1)
reference/5.1/Microsoft.PowerShell.Core/About/about_Functions_Advanced.md	✅Succeeded	View (powershell-5.1)
reference/5.1/Microsoft.PowerShell.Core/About/about_Variables.md	✅Succeeded	View (powershell-5.1)
reference/7.4/Microsoft.PowerShell.Core/About/about_Functions_Advanced_Parameters.md	✅Succeeded	View (powershell-7.4)
reference/7.4/Microsoft.PowerShell.Core/About/about_Functions_Advanced.md	✅Succeeded	View (powershell-7.4)
reference/7.4/Microsoft.PowerShell.Core/About/about_Variables.md	✅Succeeded	View (powershell-7.4)
reference/7.5/Microsoft.PowerShell.Core/About/about_Functions_Advanced_Parameters.md	✅Succeeded	View (powershell-7.5)
reference/7.5/Microsoft.PowerShell.Core/About/about_Functions_Advanced.md	✅Succeeded	View (powershell-7.5)
reference/7.5/Microsoft.PowerShell.Core/About/about_Variables.md	✅Succeeded	View (powershell-7.5)

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[surfingoldelephant]

Thanks for tackling this (and my other recent issues), @sdwheeler.

I've left a couple of comments on points I feel need addressing.

[surfingoldelephant]

The issue is not limited to digit-only parameter names. The issue applies to parameter names that start with a digit, irrespective of the characters that follow.

For example, the following is just as susceptible to the raised issue, despite it not using only decimal digits/being numeric.

function TestFunction { param ([string] $1Foo) "1Foo: $1Foo" }
TestFunction -1Foo Bar

# Broken:
# 1Foo: -1Foo

[sdwheeler]

OK, I missed that distinction. I will update the docs.

[surfingoldelephant]

Thank you!

[surfingoldelephant]

This is not accurate. The token is parsed as a string - see the AST output in the original example.

To demonstrate this in practice:

function TestFunction { param ([object] $100) $100.GetType().Name }
TestFunction -100 # String