When typing arguments for a node that has no suggestions, now the command suggestion will just report and error instead of showing the string representation of the command node that the user is completing.
Before: (tested in 19w36a) when typing /help and a space, [<command>] text floats in the suggestion area
Now: (19w46a) when typing /help and a space, an error is displayed instead.
Same thing can be replicated to other argument nodes without proper suggestions, like the path or scale for /data get or /function etc.
This "incorrect argument" report IMO is partially intended as 19w46b aims to show this error in command blocks (trailing spaces do break commands in command blocks); imo a best solution is to have the error and the suggestion both presented on client, and only present the error for command function parsing.
Linked issues
is duplicated by 8
MC-165683
Client shows the "Incorrect argument" error when the argument doesn't have any suggestions
Resolved
MC-168547
"Incorrect argument for command" when typing effect commands
Resolved
MC-168585
Some commands display an error whith spaces
Resolved
MC-172211
The teleport command showing error messages when there is no errors
Resolved
MC-173701
Scale help for /execute store is not shown until it is already written
Resolved
Attachments
Comments 14
Also, given the purpose of this error (to prevent accidental trailing spaces in command blocks/functions), we may tweak the suggestion ui to display both suggestions and exceptions in a case like this.
Other examples error images:
[media]In this case, the command cannot have a suggestion for an integer argument, and since it has no suggestion, an error is posted instead.