-
-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dynamically generate help message for slash commands in chat UI #520
Conversation
6bdd40d
to
de0ca5e
Compare
Thank you so much for opening this PR! I think the approach is good, although I think that having both the |
Thank you @JasonWeill, done in 0eb021d. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you very much for contributing this!
@meeseeksdev please backport to 1.x |
…sh commands in chat UI
…s in chat UI (#526) Co-authored-by: Michał Krassowski <5832902+krassowski@users.noreply.github.com>
…terlab#520) * Show help for custom slash commands * Morph `short_help` into existing `help` per review
…terlab#520) * Show help for custom slash commands * Morph `short_help` into existing `help` per review
Closes #436
There already was
help
property which was not used, but it was populated with longer sentences, for example:help
attribute: "Clears the displayed chat message history only; does not clear the context sent to chat providers"I can imagine that in the future we could have
/help learn
which would use the long version, so I am proposingshort_help
to prefer in the chat UI summary message shown on/help
.However, this does not have to be this way, here are some alternative options which sound good to me to:
help
as being the "short help" and rename oldhelp
tolong_help
summary
ordescription
for "short help" keeping oldhelp
as-isUser-facing changes
No changes, unless user has a custom command installed, in which case these show up after the default commands but before
/help
: