Suggestion

command /example [<player=%player%>] [<number=1>]:

Suggestion to allow short handing like with expression patterns

command /example [player=%player%] [number=1]:

Why?

Match similarity with the expression patterns

Other

No response

Agreement

• I have read the guidelines above and affirm I am following them with this suggestion.

I don't think this is something we should add. <> makes it clear when you mean to use a type argument in a command. If <> were optional, then /command [player] becomes ambiguous. Do you want the literal word "player"? or do you want a player type argument? If this is restricted to just arguments with default values, then that ambiguity is at least reduced; i doubt anyone wants the literal text of "player=%player%" in their command. However, now the argument format is inconsistent with the one carveout, and every other case requires <>. I don't think it's worth it. Unless anyone else is strongly in favor of this, I will be closing it. Thank you, nonetheless, for the suggestion.