Chat commands are:
- only available in 1x1 chats
- identified by a global unique verb
- associated with a list of arguments
- typed : free (string, float, int), constrained (query result)
- can trigger a suggestion component : reuse regular list components?
- trigger a callback when fired (call an events, visual feedback? always send a message?)
Optional arguments make sense but might be tricky to implement e.g. probably only last ones should be optional, or careful with types.
Right
Exactly that was my point about typed arguments. string, float would be free by default while events based would be constrained.