/// <summary>
/// Uses AddHeader(name, value) in a convenient way to pass
/// in multiple headers at once.
/// </summary>
/// <param name="headers">Key/Value pairs containing the name: value of the headers</param>
/// <returns></returns>
IRestRequest AddHeaders(Dictionary<string, string> headers);
--
You received this message because you are subscribed to the Google Groups "RestSharp" group.
To unsubscribe from this group and stop receiving emails from it, send an email to restsharp+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/restsharp/b6d4032c-19c5-4eff-9776-4cd5a7ef3e6a%40googlegroups.com.
Both would work for me, I see no reason not to have such a method. Concerning the parameter, I would prefer to have the dictionary to make it explicit that parameter names should be unique.
--
You received this message because you are subscribed to the Google Groups "RestSharp" group.
To unsubscribe from this group and stop receiving emails from it, send an email to restsharp+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/restsharp/5b5d94f4-bdb4-4653-a1ff-4b2becbaa8ba%40googlegroups.com.
My recommendation would be that the function that is implemented, e.g., AddHeaders, add a validation for the uniqueness of key names (irrespective of case) and throw an exception or something if this is not the case.There is utility for this function, it makes it a lot cleaner to add headers than do it onesie-twosie.
On Sun, Aug 4, 2019 at 3:51 PM Alexey Zimarev <azim...@gmail.com> wrote:
Both would work for me, I see no reason not to have such a method. Concerning the parameter, I would prefer to have the dictionary to make it explicit that parameter names should be unique.--
You received this message because you are subscribed to the Google Groups "RestSharp" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rest...@googlegroups.com.