The apidemic from gernest

apidemic's People

Contributors

Stargazers

Watchers

apidemic's Issues

Dependency management

Hi @gernest,

not very important but I thought I'd brought up adding a dependency manager like glide or dep. What's your take on it?

First of all thanks for this project, I find it pretty handy and I find the code structure nice as well. I have a made a few modifications to it to better fit my need, but before I contribute back I'd like to discuss my ideas with you.

Features I already added:

Enabled various HTTP Methods.
Enabled imitating errors by optionally providing response code probabilities.
Make 201 the default response code for POST calls to make it more REST-compliant (http://www.restapitutorial.com/lessons/httpmethods.html)

Features I'm considering adding:

Reading an initial set of endpoints from a directory based on a CLI flag / Environment variable. (Currently I call a bash file on startup that will create the endpoints via curl, not the nicest workaround)
Reading a swagger file and creating endpoints automatically. (This might be out of scope, but I'd find it useful.)
Adding optional request validation based on the swagger file read previously. (I'm least sure about this one, but this would potentially make the error imitation
Support for more API frameworks.

What are your thoughts?

In case you wondered, this is how my API structure currently looks:

// API is the struct for the json object that is passed to apidemic for registration.
type API struct {
	Endpoint                  string                 `json:"endpoint"`
	HTTPMethod                string                 `json:"http_method"`
	ResponseCodeProbabilities map[int]int            `json:"response_code_probabilities"`
	Payload                   map[string]interface{} `json:"payload"`
}