`url()` with params and `param { }` works not obvious together about kohttp

[dtropanets]

Hey. I'd say this is an issue, because it is not obvious that url extension ignores parameters. In our case, we passed the URL provided from the API and lost parameters, resulting in failed request.

[rybalkinsd]

Hi @dtropanets , could you please submit a code sample? It would be very helpful for us to see the concrete problem. We're checking our options to clarify url { } logic

[dtropanets]

What I meant is if you receive a URL from some API ("https://api.github.com/users/whatever?client_id=xxxx") and pass it to the url(), client_id=xxxx parameter will be ignored, because url() doesn't add parameters to the builder. This is not obvious, since user is expecting that the whole url will be used for request. I think, using both url() and param { } as a source of parameters is perfectly fine. As example, user can have some url (again, "https://api.github.com/users/whatever?client_id=xxxx") as a base for requests and then add additional params using param { }.

I can make a PR with this change, it should be quite straightforward.

[rybalkinsd]

I see, make sense. Added some notes and a checklist to the issue description.
PRs are always welcome!

[rybalkinsd]

https://github.com/rybalkinsd/kohttp/tree/fix/94-url-params here are several fixes over the whole codebase according to this fix. The plan is to merge them together with @dtropanets 's PR

[rybalkinsd]

0.10.0