AddUrlSegment accepts object values but internally casts to strings causing exception

[Guerra24]

This change 8e96bba#diff-5df1c2c9f9f84319d21c361a0a336251f7698927e2f1c0b0adab575fa407c6e6 simply casts object values into strings, this is causing issues since the public api accepts object values.

[alexeyzimarev]

It would also be nice if you actually follow the contribution guidelines and provide stack trace and exception details.

But, I see what happens. Will try to fix it tomorrow.

[Guerra24]

First of all thanks for the quick fix!

It would also be nice if you actually follow the contribution guidelines and provide stack trace and exception details.

Sorry about that. I thought pointing out the source of the issue and why it was an issue was descriptive enough. Will keep that in mind for next time.

[alexeyzimarev]

You're right. I got it right after looking into the links you provided. I usually scan the issue content, and when it has no stack trace, it looks incomplete to me :)

[alexeyzimarev]

Btw I made constructors for all parameter types (except the abstract one) more explicit. The old AddParameter has to, of course, accept object? but then I try converting those values to string, not cast them.

Also, AddParameter overload that doesn't accept the parameter type enum, as well as all AddXXXParameter now have explicit string or string? where it's appropriate (not files and body parameters).

[alexeyzimarev]

It will break some existing code of course... I understand that you got this error when passing something like a number or a boolean. Not sure how to fix it better. Maybe I need to return the overload that accepts object? It might lead to boxing though, need to check.

[alexeyzimarev]

Made this, and it clearly shows the boxing issue. Not such a big issue though.