Skip to content
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

not require case-sensitivity in chat commands #136

Open
jedelman8 opened this issue Jun 14, 2022 · 1 comment
Open

not require case-sensitivity in chat commands #136

jedelman8 opened this issue Jun 14, 2022 · 1 comment
Assignees
Labels
hacktoberfest status: accepted This issue has been accepted by the maintainers team for implementation
Milestone

Comments

@jedelman8
Copy link
Contributor

Environment

Any.

Proposed Functionality

Support at a minimum, the main chat command /nautobot, /meraki (two examples) to not require case sensitivity and consider it for the sub-commands.

Use Case

After seeing a live demo yesterday from a cell phone using MS Teams, it became quite difficult to execute chat commands with the automation these mobile apps have to capitalize the first letter. It would be great to add flexibility to support upper and lowercase for commands and sub-commands.

@jvanderaa
Copy link
Contributor

I'm wondering if this is a chat platform particular set up. Do we need to look at having the bot name become capitalized as part of the name in those situations (MS Teams) and other platforms. The default on Slack is to have a lower case after a slash with a Slash command.

Second place that we may be able to solve this is moving towards DMs with the bot instead of inviting to channels/rooms and slash commands.

@smk4664 smk4664 added the status: accepted This issue has been accepted by the maintainers team for implementation label Aug 4, 2023
@smk4664 smk4664 self-assigned this Aug 4, 2023
@smk4664 smk4664 added this to the 2.1.0 milestone Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hacktoberfest status: accepted This issue has been accepted by the maintainers team for implementation
Projects
None yet
Development

No branches or pull requests

3 participants