Skip to content
This repository has been archived by the owner on Sep 20, 2021. It is now read-only.

Support identifying returned resources #6

Open
giancarlopro opened this issue Oct 1, 2018 · 2 comments
Open

Support identifying returned resources #6

giancarlopro opened this issue Oct 1, 2018 · 2 comments
Labels
enhancement New feature or request help wanted Extra attention is needed
Milestone
Stable Version

Comments

@giancarlopro
Copy link
Owner

Resources

Currently we can only parse json responses.

Would be nice to parse other resources
@giancarlopro giancarlopro added enhancement New feature or request help wanted Extra attention is needed hacktoberfest Issues participating on hacktoberfest 2018 labels Oct 1, 2018
@mishakuzma
Copy link

Would like to take this on.

What other kinds of responses would we expect from a web API? JSON seems pretty ubiquitous, but I've seen HTML responses too.

@giancarlopro
Copy link
Owner Author

giancarlopro commented Oct 1, 2018 •
edited
Loading

I think xml is still used by some API's. And there's also facebook's GraphQL, i think it's a language idk.
also have api's returning images. at first would be nice to identify the resource type, maybe from a http header, and from there parse the content or raise an exception maybe.

What do you think?

@giancarlopro giancarlopro removed the hacktoberfest Issues participating on hacktoberfest 2018 label Oct 11, 2018
@giancarlopro giancarlopro added this to the Stable Version milestone Oct 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Milestone
Stable Version
Development

No branches or pull requests
2 participants
@giancarlopro @mishakuzma