Skip to content

Handle deserialization based on content-type response header #17

Open
@demianbrecht

Description

@demianbrecht

Deserialization of response data when swapping the code for access token is currently horribly naive. Instead, it should be able to rely on the response content type to determine deserialization method.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions