Experimental - endpoint can provide own  base route
for complete flexibility of where the request goes at runtime
Refactoring for clarity
Fix typo in last commit
Hm... more flexibility but I'm not sure about this one
Remove all the Obsolete things!
There only was one
Better naming: OAuthToken and OAuthTokenSecret
For OAuth fields on Request data object
Merge pull request #184 from AnthonySteele/remove-obsolete

Remove all the Obsolete things!
Added release notes for 4.0 in markdown
Updated release notes for 4.0
Merge branch 'master' into provide-base-route
Decided that we don't need a RequestData to the IBaseUriProvider
there are more than sufficient points of flexibility without it
Merge pull request #185 from AnthonySteele/release-notes

Release notes
Refactoring, added simple (string) base uri extension
Integration on providing a base route
Demonstrating contacting an arbitrary url
Simpler design as discussed
- DTOs can't implement IBaseUriProvider any more (ok, they can, there's just no reason to any more).
- ApiBaseUriProvider now does the task of deciding which of the secure & regular IApiUri endpoints is to be used
- therefor IBaseUriProvider needs the request data (at a stage before secure fields are filled in)
Moved BaseUri code into Requests namespace
as that's what it's part of
and there are 3 files now, too many for root folder
Payments#1021 Added 3005 error code to support label compliance work.
Merge pull request #188 from bnathyuw/master

Payments#1021 Added 3005 error code to support label compliance work.
Fix tests which were failing
due to content takedown and cdn url change
Merge pull request #191 from AnthonySteele/fix-integration-tests

Fix inegration tests