SaveConfig websocket event does not save/update config about gocryptotrader HOT 3 CLOSED

By default Go will only unmarshall JSON data which it knows about (unless just put into an interface{}) so any extra fields added will be ignored with no failure or error by design. Support specifically has to be added for it. Out of curiosity, are seperators sent in the extra data for currency pairs?

from gocryptotrader.

Yeah cool. Those fields are for me to easily handle things in the front-end. I strip any known seperators to be able to compare enabled currencies.
Good to know that the extra JSON isn't considered. GCT server doesn't need to care about it.

from gocryptotrader.

SetConfig cannot save if there are any warnings. I think that is fine, however, the reason for the warning I think should be removed.
After looking at WS response I got the following:
{"event":"SaveConfig","data":"OK","error":"WARNING -- SMS Support disabled due to default or empty Username/Password values."}

I feel like this should be removed. If a user runs GCT for the first time using front end, they will be unable to save until they modify the SMS details even if they do not want to change/use SMS settings. So a user will have to put gibberish into SMS settings to get past this warning.

This also applies to enabled contacts. These warnings should only come up if SMS support is enabled:

On the upside, I now display any errors to the user:

from gocryptotrader.