Closed hcoyote closed 6 years ago
Thanks for suggesting this - it would be good to separate the storage of the user credentials and the RTM CLI configuration. I just renamed the extra config file to use ~/.rtm.config.json by default since it could be used to store other config properties in addition to the aliases
This PR allows placing aliases in a separate config file ($HOME/.rtm.aliases.json) so you have the option of independently storing those in source control. Putting the $HOME/.rtm.json into source control is challenging because it contains private access keys to the RTM account (and it's good security practice to not store keys in github), so you have to jump through hoops in order to save your aliases.
This is a simple work around for this, by having a second file read upon startup that loads in the aliases file after the default user config is loaded. There may be a better way, but this was the most straight forward.