BotConfig example

[davechurchill]

BotConfig example

[davechurchill]

a. The reason I have the .txt extansion is because with UAlbertaBot when I had a .json file, I received a surprising number of emails / questions about what program you use to open it, etc. So I left it as a .txt file for it to be more obvious. The general computer / programming skill of many users is not that high.

b. I'll think about this, but again, people will skip some instructions, run the bot, and it will say that the config file is missing and ask questions about it. I agree with the principle of what you're saying, just not sure if this is the way I want to go about it

[alkurbatov]

a. The reason I have the .txt extansion is because with UAlbertaBot when I had a .json file, I received a surprising number of emails / questions about what program you use to open it.

I see, thank you for clarifying this.

Regarding #b it just cause some inconvenience during dev, i.e. I have to cast:

$ git stash
$ git fetch
$ git merge upstream/master
$ git stash pop
# Resolve conflicts in the config.

Also I should be careful to not commit the config accidentally.

[alkurbatov]

people will skip some instructions, run the bot, and it will say that the config file is missing and ask questions about it.

We can workaround it by searching BotConfig.txt first and BotConfig.example.txt next :) But I believe there should be a better solution.

Who are those people who use the bot? They checkout the sources or use something like .exe in an archive? For the latter it is possible to make special command (or script) which pack everything with proper names.

[davechurchill]

I agree with you that a change should be made, just gonna think for a while about how to do it

[stolencatkarma]

you could change it to BotConfig.example.txt and if there isn't one at runtime just rename the file to BotConfig.txt and continue. This let's new people just run it and have it work.

my 2 cents.