refactor(commands): standardize parameter conventions

This commit is contained in:
tiennm99 committed 2026-07-21 14:51:28 +07:00
1 parent a211b7f8b7
commit d2c3129d41
10 files changed
+329 -21

No files matched your search

+2 -5
View File
@@ -29,11 +29,8 @@ deleting commands, update all related surfaces:
- tests for registration, handlers, and command menu behavior
- README/docs when behavior changes are user-visible
Use lowercase, descriptive parameter names in command metadata and usage text.
Include units or currencies when meaningful (for example, `<vnd_amount>`), use
`[...]` for optional input, append `...` for remaining free text, and use
parentheses to document structured input (for example,
`<ratio(owned:new)>`). Keep metadata, usage errors, examples, and tests exact.
Follow `docs/command-parameter-conventions.md` for all command parameter
metadata and usage text. Keep metadata, usage errors, examples, and tests exact.
Telegram's native menu and `/help` show command syntax plus the summary without
example invocations.