Change the default behavior of selecting default configurations

[ghost]

Hi everyone,

I noticed that current init process requires an explicit parameter to use YAML config.

Therefore, to allow usage of YAML as default config, here is my proposal on this section that:

When user has explicitly specified a config using -config parameter:

1. check whether it is a JSON or YAML file. If it is not JSON nor YAML, raise a fatal exception (line 34);
2. read file. If it does not exist or something wrong happened during reading, raise a fatal exception (line 39-45);
3. build a proxy based on it. If it is not valid, raise a fatal exception (line 51);
4. run the proxy. If something happened, raise a fatal exception (line 55);
5. if nothing wrong happened, return nil marking successful reading and parsing.

When user has not explicitly specified:

My proposal will try three candidate: config.json, config.yml, and config.yaml.

For each candidate:

1. 1 is definitely passing;
2. read file. If the file does not exist (indicated by err.Error()), raise a warning that the file is not there and move to next candidate (line 40-42 and line 78); if anything else happened, raise a fatal exception is raised (line 44);
3. 3, 4, and 5 are the same.
4. If all three candidates cannot be loaded, raise a fatal exception (line 82) showing that no default candidate is provided.

There is one thing to do: I have no idea what OS X raise when a file is not found.

I am looking forward to your ideas and feedback.

Regards,
Chinese White Dolphin

[Loyalsoldier]

Thanks! I have made some refinements.

[ghost]

It is me to say thank you. It is an overhaul :-D.