Inspired by elasticsearch ?pretty flag.

http://localroast:8080/users?pretty should return a properly indented JSON.

Hi there,
I have experimented some with your wonderful application, but have an issue that I would like to take up for discussion.

I'm trying to use localroast for mocking API data for one of my applications on localhost, but unfortunately when running it I get a CORS error.

Would it be possible to implement an access control allow origin header? Something like this:

Access-Control-Allow-Origin: *

This would make it possible to use it to mock data in an application running on a different localhost port.

Thanks in advance!

It would be great to have auto-generated values for the responses especially for list endpoints. Mocking a large response list is otherwise just a very dumb task

https://swagger.io/specification/

Questions:

• which version?
• json or yml?
• how to differentiate between openAPI file and existing json or yml if supported

Useful to support multiple responses, such as success, failure, errors.

Options:

• Randomly pick from the responses
• Round robin
• Weighted

Thumbs up if a .yml file would be useful.

Suggestions on what the format of .yml would be appreciated too. One idea I had was to work based on swagger, as it's a common API documentation format.