Floating point values are converted with cultural settings

[tmm360]

For example, the double in some countries (as mine) is converted to string with a comma ',' instead of a dot '.' between integer and decimal digits, and encoding url it is converted to %2C.
This is an issue because decoding value first it is received as an array of two integers, and not in every context I can parse values before than they are decoded.

[darrelmiller]

Thanks for the info. I'll look into it and try and include a fix in the next release.

[darrelmiller]

The URI Template class handles strings, IEnumerable and IDictionary<string,string>. When the parameter is not one of those types, we simply call object.ToString(). Unfortunately, that method doesn't have a Culture property.  If we can identify which types need to be special cased, and that set of types covers a large enough set of cases, then we could add handling for that. However, this is a can of worms. I'm sort of wishing I had stuck with my original idea of requiring parameters to be explicitly converted to strings by the application before providing them to URI template.

[tmm360]

Actually I've solved applying this simple workaround to value value.ToString().Replace(',', '.'). You could handle floating point values, that at moment they are the only that are showing issues. Other value types with cultural settings don't occur to me...
I like very much capability of assign a simple value, library handles cases and perform mechanic normalizations, I don't like idea of have to convert values to string every time. It should be very painful. Thank you for your work!

[baywet]

@darrelmiller we could start with all the number and date based types, that is:

• datetime
• datetimeoffset
• timespan
• numerics

by adding a switch expression based on type inference here

what do you think?