Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle non-JSON responses from the API #59

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

louisameline
Copy link
Contributor

Facebook API endpoints such as /me/picture return things other the JSON. The library made the choice to believe any non-JSON response is an error, which is not the case.

I introduced an optional fourth 'reqOptions' parameter for the api/napi method. Currently, there is only one option in there : accepting responses of content-type other than json (see the updated Readme). You can provide a content-type string, an array of content-type strings, or just the string 'any'. I added the encoding: 'binary' option to the request module to allow pictures, videos and such.

…eated allows us to accept non-json (binary for example) resources sent by the API, like photos or videos
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant