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

Support for application/json+fhir #127

Closed
steveswinsburg opened this issue Apr 24, 2017 · 5 comments
Closed

Support for application/json+fhir #127

steveswinsburg opened this issue Apr 24, 2017 · 5 comments

Comments

@steveswinsburg
Copy link

I have a service which returns application/json+fhir as the content type. This does not pretty print, presumably because there is no support for that specific content type. The format is pretty much identical to application/json - it would be great if the pretty printer could parse that format.

@mmattozzi
Copy link
Owner

The app actually assumes any content type that ends with +json should be pretty printed as JSON (in addition to application/json). I didn't think about covering the reverse of that, json+*. Seems like there is some discussion about this WRT json+fhir here: hapifhir/hapi-fhir#445

Should be easy enough to add however.

@mmattozzi
Copy link
Owner

Will add this to the next release.

@mmattozzi
Copy link
Owner

Fixed in https://github.com/mmattozzi/cocoa-rest-client/releases/tag/1.3.17

@steveswinsburg
Copy link
Author

Thanks for fixing this ⭐️. In the 'Check For Update' option it says 'Cocoa Rest Client 1.3.15 is currently the newest version available.' I can manually update but is there some service that needs to get the new version number for the auto update?

@mmattozzi
Copy link
Owner

mmattozzi commented May 10, 2017

Between version 1.3.15 and 1.3.16, I bumped the required OS from 10.10.3 to the latest update of El Capitan, 10.11.6 for the auto-updater. The build target is still just 10.11 in the code, but I don't have the capability of testing at anything lower than 10.11.6 so I just set that as the requirement. By the way, the next official release will be Sierra only (looking ahead to 10.13 probably coming out this fall, I don't want to ever support more than two versions of macOS).

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

No branches or pull requests

2 participants