Currently, constraints like "a question must only have up to n characters" are fixed and hard coded. This is a problem because:
it has to be updated every time new options are added
it restricts users (e.g., it's not possible to have a very long question but only a few short options in contrast, even though it would fit in a message)
I therefore suggest that the lengths of the settings for each command invocation are summed and added to a constant (how much space the additional message parts like the bar chart will need) and if that exceeds the maximum character limit, reject the command.
Furthermore, the max option key length and key separator should be made configurable through config.edn, because both are currently not optimal and I would like to experiment with them to find the best settings.
Currently, constraints like "a question must only have up to n characters" are fixed and hard coded. This is a problem because:
I therefore suggest that the lengths of the settings for each command invocation are summed and added to a constant (how much space the additional message parts like the bar chart will need) and if that exceeds the maximum character limit, reject the command.
Furthermore, the max option key length and key separator should be made configurable through
config.edn, because both are currently not optimal and I would like to experiment with them to find the best settings.