Lower ExprParse priority to PME

[bluelhf]

Problem

Currently, uuid of text argument parsed as player is parsed as (uuid of text argument) parsed as player through the converter chain ((String -> World)ExprUuid -> String)ExprParse.

This happens because ExprParse has higher priority than property expressions: ExprParse has priority COMBINED, as compared to properties' PropertyExpression.DEFAULT_PRIORITY. This default priority for property expressions is between COMBINED and PATTERN_MATCHES_EVERYTHING (hereafter PME).

ExprParse is thus identified first when parsing the expression, leaving the remaining string uuid of text argument to be parsed by ExprUUID via a conversion to World.

Solution

The priority of ExprParse is lowered to PME, which means property expressions now take precedence over the parse expression. uuid of text argument parsed as player will be parsed as uuid of (text argument parsed as player).

Testing Completed

• Ran quickTest to verify no current tests break as a result of the change
• Thought really hard for some minutes about ways to break it, but couldn't come up with any

Supporting Information

It seems unlikely that something could break, as it would require a string property that is valid both on strings and on the result type of ExprParse. The trivial case is parsing as text, but this is forbidden by ExprParse.

---

Completes: #8541
Related: none
AI assistance: GitHub Copilot tried to autocomplete but was not used due to lacklustre performance