In M, it is valid to name function parameters after M types, as parameter names will not be interpreted as type names when defining a function’s signature. However, syntax highlighting does not seem to make this distinction.
Expected behavior
In a function signature, parameters that have the same names as M types should be syntax highlighted the same as parameters with other names.
Actual behavior
Parameters with the same names as M types are highlighted differently.
Notice below how the red-underlined parameter names (which are identical to M type names) receive different syntax highlighting than the green-underlined one.
To Reproduce
In VSCode, create a Power Query file containing the following content:
(table as table, function as function, a as number) as any => ...
In M, it is valid to name function parameters after M types, as parameter names will not be interpreted as type names when defining a function’s signature. However, syntax highlighting does not seem to make this distinction.
Expected behavior In a function signature, parameters that have the same names as M types should be syntax highlighted the same as parameters with other names.
Actual behavior Parameters with the same names as M types are highlighted differently.
Notice below how the red-underlined parameter names (which are identical to M type names) receive different syntax highlighting than the green-underlined one.
To Reproduce In VSCode, create a Power Query file containing the following content: