You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Change it to be !reply [msgid]
Only downside I can think of right now is any possible code duplication between the cases, but it'd also let us remove some command parsing logic.
Another issue: users may be used to the syntax of !send reply
Few options:
Make a full change and make an announcement
Implement the shortened command while keeping the old one, and remove it in the next release so that users are acclimated
If they use "send reply", send a help message telling them it has changed
The text was updated successfully, but these errors were encountered:
Good idea! I'm in favour of making an announcement of the change, as well as sending them a help message telling them it's changed if they use the old syntax.
Just thought of this: using !reply msg won't work if we want to send to deep-talks, since the word "reply" replaces "send-deep". The same problem will exist for other channels once we implement scalability.
What problem are you facing?
!send reply [msgid] feels unnecessarily long
What can we do to fix that problem?
Change it to be !reply [msgid]
Only downside I can think of right now is any possible code duplication between the cases, but it'd also let us remove some command parsing logic.
Another issue: users may be used to the syntax of !send reply
Few options:
The text was updated successfully, but these errors were encountered: