Skip to content
This repository was archived by the owner on Feb 6, 2021. It is now read-only.

Client should not parse for content types it cannot handle #55

Open
2 tasks
BradMclain opened this issue Aug 15, 2016 · 0 comments
Open
2 tasks

Client should not parse for content types it cannot handle #55

BradMclain opened this issue Aug 15, 2016 · 0 comments
Assignees
@BradMclain
Labels
enhancement

Comments

@BradMclain
Copy link
Contributor

BradMclain commented Aug 15, 2016 •
edited
Loading

  • Do not parse
  • Show warning/error
@BradMclain BradMclain added this to the 2.0.1 milestone Aug 15, 2016
@BradMclain BradMclain self-assigned this Aug 15, 2016
@BradMclain BradMclain changed the title Client should not parse and show warning for content types it cannot handle Client should not parse for content types it cannot handle Aug 15, 2016
@BradMclain BradMclain modified the milestones: 2.0.2, 2.0.1 Oct 5, 2016
@BradMclain BradMclain removed this from the 2.0.5 milestone Aug 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@BradMclain BradMclain

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@BradMclain