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 XML & XML Schema #57

Open
danascheider opened this issue May 29, 2016 · 0 comments
Open

Support XML & XML Schema #57

danascheider opened this issue May 29, 2016 · 0 comments

Comments

@danascheider
Copy link
Owner

Summary

Although Rambo is an opinionated tool and its opinion is that REST > SOAP, the reality is that sometimes our users will simply need to handle XML - especially, they will need to accept XML requests. Rambo currently has no functionality supporting XML and would raise ugly errors if the generator were to be run against a RAML file including XML or XML Schema. Rambo should accept and generate XML as needed.

Expected Behavior

When given a document with XML or XML Schema, Rambo should handle these formats as well as it handles JSON. This would include not only creating and destroying XML files when required, but also generating XML from XML Schema to make requests.

Current Behavior

Rambo assumes that all schemas and examples are in JSON format, going so far as to create all example and schema files with the .json extension without checking the actual file format, as well as calling .to_json in the generated tests without checking the actual data type.

Context

We are developing the Rambo MVP against Repaymnt Estimatr, a proprietary app owned by my employer, which is sponsoring the Rambo project. Now that the MVP is wrapping up, we are setting our sights on a second app, Mandolin. Mandolin accepts JSON request bodies and returns XML responses. This is not how I would prefer that it be done, but it is what is being handed to me.

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

1 participant