It might be an idea to introduce an optional, nondestructive read-only mode, which when in effect will disallow all API methods that are destructive or that modifies state.
The idea is that you have a token for a workspace but you want to be sure that you don't do damage by mistake. Like when running files.delete without being careful.
This should be configurable directly with the config command with --set-read-only <True|False>. Every command must then check for config.read_only() and/or we put it into SlackAPI so that for such methods it will simply not send the request, and instead write to log that it didn't do it due to read-only mode.
When in read-only mode, the prompt should state this somehow, like
It might be an idea to introduce an optional, nondestructive read-only mode, which when in effect will disallow all API methods that are destructive or that modifies state.
The idea is that you have a token for a workspace but you want to be sure that you don't do damage by mistake. Like when running
files.deletewithout being careful.This should be configurable directly with the
configcommand with--set-read-only <True|False>. Every command must then check forconfig.read_only()and/or we put it intoSlackAPIso that for such methods it will simply not send the request, and instead write to log that it didn't do it due to read-only mode.When in read-only mode, the prompt should state this somehow, like