Increase visibility of LinkedIn REST errors #30
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… 403. The usage of Faraday was hiding the REST error messages from LinkedIn and it was difficult for me to debug my app. Exposing the errors should help others get their apps working.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had a hard time getting started with the linkedin-oauth2 gem because I couldn't see what errors LinkedIn was getting. Just seeing a 400 or 403 was too opaque for me, so I extended the raise_error class to throw specific errors on a 400 or a 403.
I hope that exposing the errors can save new users some trouble and allow them to quickly get their apps working.