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

Task Name for Commands Should Not Be Case-Sensitive #15

Open
rumdood opened this issue Feb 8, 2024 · 1 comment
Open

Task Name for Commands Should Not Be Case-Sensitive #15

rumdood opened this issue Feb 8, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@rumdood
Copy link
Owner

rumdood commented Feb 8, 2024

When a task is created from the chatbot commands (i.e. /create), the casing used is what gets echoed back to the user, but the API's GET calls are case-sensitive and tasks are created in all-lower-case.

Scenario:

User: /create MyTask
...[Q&A to build task]
Bot: Created MyTask!
User: /complete MyTask <--- Backend receives a 404 error because the task MyTask is not found by the API
User: /complete mytask <--- Succeeds

@rumdood rumdood added the bug Something isn't working label Feb 8, 2024
@rumdood rumdood self-assigned this Feb 8, 2024
@rumdood
Copy link
Owner Author

rumdood commented Feb 8, 2024

There are actually two issues here. One in that the task can't be complete unless the user sends the task name in lower case and the other that the bot does not actually respond when it receives the 404 error. No feedback is given to the user at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant