Code cleanup and pathname issue

[floatdrop]

There were some 💩 code (by me) like this:

arg.path = (arg.path ? arg.path.split('?')[0] : '') + '?' + (typeof query === 'string' ? query : querystring.stringify(query));

Or this:

var parsedUrl = typeof url === 'string' ? urlLib.parse(prependHttp(url)) : url;
// ...
url = typeof url === 'string' ? prependHttp(url) : urlLib.format(url);

Which was hard to maintain and read.

Main reason for this code - there was two different arguments for get function - first contains request options (as object or as string) and other gets got options.

This logic was replaced by merging url and opts arguments in got function into one. Because (on redirect) we can reassign parsed request options.

In the process redirect event was fixed - it was emitting old opts that was not from redirect itself.

#72 was fixed by reassing path to pathname (if pathname is present). I don't know, if this is right thing to do, but because of difference in http.request and url.format + url.parse we have to normalise options or use another url.format implementation.

//cc @sindresorhus @sindresorhus @kevva

[floatdrop]

Side-effect: now you can specify got options in first argument:

got({host: 'google.com', timeout: 2000});

[sindresorhus]

Side-effect: now you can specify got options in first argument:

Should this be documented?

[sindresorhus]

Super nice cleanup and improvements @floatdrop :D

[sindresorhus]