Your custom command is now flagged when its name clashes with a builtin command's alias.
What's wrong with this entry?
A user or plugin command whose name matches a builtin command's alias is now detected as a collision instead of quietly shadowing it.
- Building the set of taken command names adds each command's
aliasesentries as well as its name. - The same alias awareness feeds the new tip filtering check (
n.name === e || n.aliases?.includes(e)).
for (let g of h.aliases ?? []) s.add(g);
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
A crashing slash command now tells you it crashed
Both mention slash command
-
v2.1.234
A command can decide from its arguments whether it counts as sensitive
Both mention slash command
-
v2.1.234
A slash-command grouping for a command that does not exist
Both mention slash command