[Feature] Statically parse selectors before executing tests

[IanVS]

This is just an idea, but I found that sometimes I have a small typo in a selector, and it doesn't error until playwright actually tries to execute it, then I get a parse error. It might be nice to perform a static analysis of the selectors up-front, to fail fast. This might not always be possible (e.g. if the selectors aren't just string literals), but it might be useful at least as a "best effort" attempt.

[mxschmitt]

Could you share with us what kind of typos you mean? Might be something for the ESLint plugin (#9474) or for the VSCode extension.

[enricopolanski]

I guess something malformed as locator(foo[bar=baz).

[IanVS]

Exactly. I think I had an extra ] somewhere.

[mxschmitt]

Folding into #16972

[IanVS]

I think there could be value to others who do not use vscode if this were done at the very start of the test run itself, but I do use vscode, so I won't complain. :).