Type: Bug
Summary:
Second "/send" command is shown in commands list if chat contains 1 or more Request messages sent to this contact.

Only one /send command is shown
/send
/request
/send
are shown in the list
reproduced in last nightly from 2/19/18

@annadanchenko This is actually not a bug, only bad UI - whenever command request is received, it's added to the "open requests" for you, and those are merged with standalone "commands" in the suggestion list.
So when somebody requests from you twice, let's say /request 2 and /request 1, those are two different command request, with different parameters (2 ETH in first case, 1 ETH in second case), and when you click on any of the request pulsing bubbles, /send command is loaded with correct arguments.
Now we also display command requests in the suggestions list, where we merge them with normal commands, we could de-duplicate them, but in that case, which parameters should be pre-filled for /send command if you have multiple /requests outstanding, parameters of the last request, or first request ?
I see two ways how to solve it:
@janherich I would stick to option 1 (do not show command requests in the suggestions list) because current way is already broken, so users can't get any useful effects from using the second /send
For the future - we might need to implement option 2 based on UX/UI feedback and new designs.
I vote for option 1 as well
Most helpful comment
@janherich I would stick to option 1 (do not show command requests in the suggestions list) because current way is already broken, so users can't get any useful effects from using the second /send
For the future - we might need to implement option 2 based on UX/UI feedback and new designs.