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

[FEATURE] More receptive responses on non-fatal failures #6

Open
luphoria opened this issue May 3, 2022 · 0 comments
Open

[FEATURE] More receptive responses on non-fatal failures #6

luphoria opened this issue May 3, 2022 · 0 comments

Comments

@luphoria
Copy link
Owner

luphoria commented May 3, 2022

graim currently essentially ALWAYS tells you that the operation was completed successfully. While this is fine 90% of the time (usually, any non-fatal errors are not really errors but simply non-issues), I think it would be a lot more useful for the bot to at least warn you in the situation that something has gone wrong partially.

For example - when a user is banned, graim will attempt to ban them from discord and matrix. As long as the command isn't improperly formatted, graim ALWAYS responds with a success - even if there was not actually a success in the action. For example, if graim's power level isn't high enough in every room, then it will not be able to ban the user - however, there is no way for the end user to know the interaction failed, without logging on Matrix themselves and seeing the ban event in the log.

Mostly I am using this issue to track a long-term implementation of more reception from graim, because this is a big design issue that I am currently completely ignoring. First, I need to figure exactly how I want output to show (should I log in every room/channel individually that it failed in? Should I print out another message after the ban success showing any warns?)

Any outsider input is greatly appreciated!

I am going to be tracking this development in the commit names, so it should be easy to follow progress on this specific development.

@luphoria luphoria pinned this issue May 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant