The tests are only for functions which do not require valide access tokens and
Id's for DNSimple or Telegram. I'm under the impression, the functions which
require valid access tokens and Id's will be better served by testing them
manually. I don't want to run the risk of including personal secret tokens with
the repositories commit history.
This new CLI feature allows the user to check the schema of their configuration
file. The check is to make sure their file's schema is correct. It doesn't check
to make sure their access tokens and Id's are valid. This feature is just a
quick way to make sure you've not mangled your configuration file by deleting a
comma or made a typo. when naming a key, in the JSON object.
I changed the hash table key from the 'last-recorded-ip' to a string from a
quoted string (I.E. 'last-recorded-ip). This fixed the bug which added a second
'last-recorded-ip' to the config. JSON file.
I, also, did a bit of code clean-up (removing commented out code) and fix the
incorrect file path bug for the update-conf-file-to-latest-ip function.
For some reason, I used the read-config-file function when I just needed to pass
the file path for the config. file, when calling the update-ip-addresses
function. This commit fixes that error.
The code still needs to update the configuration file so the last recorded IP
address is stored after every run. There is a slight bug where the code writes a
'new' entry of the IP address whilst keeping the old IP address version around
in said file.
Craig Oates