SethFalco/commandler
SethFalco/commandler
Watch
1
Code Issues 44 Pull requests Projects Releases Packages Activity Actions

When a Hidden Command Fails, Users Shouldn't Know #75

New issue
Open
opened 2019-11-10 01:02:29 +00:00 by Ghost · 0 comments
Ghost commented 2019-11-10 01:02:29 +00:00 (Migrated from codeberg.org)
Copy link

Sub-Project

This is regarding:

  • core
  • validation

Description

When a command is performed which is hidden, or marked in some has validation because it doesn't want users to be able to see how to do it or to be able to perform it, Commandler still tells the user what they did wrong as if it's something they would normally be able to do.

For example, in Alexis there is a command that an admin can do to shut it down via $dev shutdown, while users aren't able to perform this, users shouldn't be able to prompt responses out of it regardless of if they tried to do it, or did it wrong.

<!-- You'll see comments around here, don't mind these; they won't get displayed! Please take requests for help anywhere but the issue board, this is reserved for tasks, feature requests, or bug reports. If you are in need of help, please try ask on StackOverflow/Reddit, or join the Discord. --> <!-- Can you specify which sub-project(s) this is relevant to? If you don't know, or this is a proposal for a new sub-project, you can delete this. --> ### Sub-Project This is regarding: * core * validation <!-- Explain what this is about, try to use full sentences, and make your point clear. If this is a feature request, please try to make the motivation behind the request clear. If it's a bug report, please make sure we have all the information required to reproduce the bug. --> ### Description When a command is performed which is hidden, or marked in some has validation because it doesn't want users to be able to see how to do it or to be able to perform it, Commandler still tells the user what they did wrong as if it's something they would normally be able to do. For example, in Alexis there is a command that an admin can do to shut it down via `$dev shutdown`, while users aren't able to perform this, users shouldn't be able to prompt responses out of it regardless of if they tried to do it, or did it wrong.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
i18n
4.0.1
Labels
Clear labels   
bug
Something that's not working as intended in an existing project's functionality.

  
feature-request
A brand new feature for an existing project.

  
upstream
Should be resolved through an upstream contribution.

No labels
bug
feature-request
upstream
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
SethFalco/commandler#75
No description provided.