-
Notifications
You must be signed in to change notification settings - Fork 50
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
'application/json' hard-coded as response body type #12
Comments
jenner
added a commit
to jenner/ramlfications
that referenced
this issue
May 26, 2015
- The responses bodies map is now accepting more then just 'application/json' media types. If there's no valid media type, the default one is used and the body spec is inspected for 'schema' and 'example' parameters - Added XSDs for thingy and thingy-list - Added parser tests wrt response bodies parsing
jenner
added a commit
to jenner/ramlfications
that referenced
this issue
May 26, 2015
- The responses bodies map is now accepting more then just 'application/json' media types. If there's no valid media type, the default one is used and the body spec is inspected for 'schema' and 'example' parameters - Added XSDs for thingy and thingy-list - Added parser tests wrt response bodies parsing
Fixed in 740647e |
econchick
pushed a commit
to econchick/ramlfications
that referenced
this issue
Jun 5, 2015
- The responses bodies map is now accepting more then just 'application/json' media types. If there's no valid media type, the default one is used and the body spec is inspected for 'schema' and 'example' parameters - Added XSDs for thingy and thingy-list - Added parser tests wrt response bodies parsing
econchick
pushed a commit
to econchick/ramlfications
that referenced
this issue
Jun 5, 2015
- The responses bodies map is now accepting more then just 'application/json' media types. If there's no valid media type, the default one is used and the body spec is inspected for 'schema' and 'example' parameters - Added XSDs for thingy and thingy-list - Added parser tests wrt response bodies parsing
econchick
pushed a commit
to econchick/ramlfications
that referenced
this issue
Jun 5, 2015
- The responses bodies map is now accepting more then just 'application/json' media types. If there's no valid media type, the default one is used and the body spec is inspected for 'schema' and 'example' parameters - Added XSDs for thingy and thingy-list - Added parser tests wrt response bodies parsing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The [resp_body](https://github.com/spotify/ramlfications/blob/master/ramlfications/parser.py#L927-L948 function) returns only bodies of type 'application/json', however the RAML spec state that you may have more then one media type in a response specifications (e.g. epending on your request's Accept header)
The text was updated successfully, but these errors were encountered: