Eric Newton
Eric Newton
I dont think the library supports that at the moment. Might try looking through the code to find out. I didnt write that part of it, was added by someone...
What exactly do you mean? Doesnt this code do reverse geocoding? ```c# var request = new GeocodeRequest(); request.Location = new LatLng(30,-70); var service = new GeocodeService(); var result = service.GetResponse(request);...
One issue is going to be types specific to the Service. I believe those should stay in their respective service namespace, because of the same consideration of keeping the core...
Definitely. Currently doesnt deal with rate limiting at all. The tricky part is informing the consumer of the api that rate limiting is happening. Perhaps first phase is a RateLimitException...
An additional way could be that you can configure the library to use a strategy for accessing the webservice and allow the developer/consumer to pick which one to use. Default...
And the ExponentialBackoffHttpStrategy would almost be necessary to have async/await implementation as well since we'll be throwing waits into the mix.
When looking on [nuget.org](https://www.nuget.org/packages?q=uri), search reveals several "proper" RFC 3986 implementations... @richardthombs or perhaps https://github.com/balazsbotond/FluentUriBuilder instead of the internal QueryStringBuilder and do any
Doesnt the Newtonsoft Json parser library have an option similar to this? Like CamelCaseProperty or something? I'm going to look and update this comment after EDIT: So after a bit,...
Between jobs: Lol, as I am, too...
Yes I believe its in the newer Jsonsoft's. I was going to try to tackle this. UPDATE: Yes, SnakeCaseNamingStrategy is in Json.Net v10+. I'm slightly worried about moving so far...