postmoogle/bot
Slavi Pantaleev a057654962 Put command access checks on the command level
Checking using `settings.Allowed` is odd. Not all commands are related
to setting configuration settings. Admin commands are coming in the
future, for which this is certainly not the case.

We now do access checks early on (during command processing), so command
handlers can be clean of access checks. If we're inside of a command
handler, the user is privileged to run it.
2022-08-29 10:27:53 +03:00
..
access.go Put command access checks on the command level 2022-08-29 10:27:53 +03:00
bot.go Put command access checks on the command level 2022-08-29 10:27:53 +03:00
command.go Put command access checks on the command level 2022-08-29 10:27:53 +03:00
context.go refactor to context, remove sentry spans 2022-08-25 22:31:12 +03:00
data.go add 'nofiles' option, refactored bot.Send(); fixes #2 2022-08-26 16:11:08 +03:00
email.go remove debug 2022-08-28 09:37:32 +03:00
message.go proposed changes 2022-08-27 21:59:58 +03:00
mutext.go add per-room mutex, possibly fixes #8 2022-08-27 22:10:22 +03:00
settings.go Put command access checks on the command level 2022-08-29 10:27:53 +03:00
sync.go Put command access checks on the command level 2022-08-29 10:27:53 +03:00