Closed DavidGoodwin closed 1 month ago
Thank you for this PR. Could you tell me why this is needed? What if we update the documentation to be extra clear that one should use the path as parameter?
Oh - I was trying to use one of the V2 APIs, and was just pasting in the URL from the page (see e.g. https://developer.linkedin.com/docs/guide/v2/ads/create-and-manage-accounts) as the resource.
If you can document it then fine.
What's in this PR?
If someone passes e.g. https://api.linkedin.com/v2/whatever in as the resource parameter, then the underlying code will try and request https://api.linkedin.com/https://api.linkedin.com/v2/whatever ... which unsurprisingly doesn't work.
Why?
I wasted some time wondering why it wasn't working ....
Example Usage