Semantic Highlighting should recognize a function that doesn't follow noun-verb format if defined in the same document

[JustinGrote]

Prerequisites

• I have written a descriptive issue title.
• I have searched all issues to ensure it has not already been reported.
• I have read the troubleshooting guide.
• I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.

Summary

See visual

PowerShell Version

7.2.1

Visual Studio Code Version

Insiders

Extension Version

preview

Steps to Reproduce

function test {}

test

F1 -> Inspect Editor Tokens and Scopes -> hover test and see that support.function scope is missing

Visuals

Logs

No response

[JustinGrote]

This looks like it has been fixed, not sure where.

[andyleejordan]

Probably in the symbol rework from abound this time last year. Though are you sure this was specifically "Semantic Highlightling" and not just regular highlighting?

[JustinGrote]

@andyleejordan note the "semantic token type" in the inspector, and yes I A/B tested it with semantic off.

[andyleejordan]

Weiiird then because we haven't touched the semantic highlighting whatsoever. Oh well, I like that it's fixed!