Joan López de la Franca Beltran

Yeah, a verbose mode (-v / --verbose) with that kind of logs is a really good idea. Could you share with us how these logs would looks like? Thanks!

IMHO, logging everything isn't the best approach. We might provide some useful data (imposter file, path, params or the satisfied regex) instead, in order to let the user know why...

> I miss the log functionality as well. I would like to be able to see the requests in the logs. For this, log levels could be specified for the...

Hey, Yup, we're completely open to suggestions. Maybe we can define multiple response mechanisms. IMHO, both (the one defined on the issue description and the one you mentioned) can coexist....

> @joanlopez is this issue still open? > I'd like to start working on this one but I see in the documentation that we support dynamic responses and this issue...

Hi @NavaneethNKMN, First of all, thanks for reaching us! I'll be happy to try to help you. Let me ask you some questions to get additional context: - What Killgrave...

> > > * What do you think about moving the `responseMode` to the imposter's level or to make the `response` field an object with `mode` and `payloads` fields within?...

Hi @donbachi, I assigned you, so it's time to 🚀 Please, feel free to ping us if you have any doubt or need. Thanks!!!

Hi @fbachan, thanks for reaching us! Have seen the support for JSON schema? 👇🏻 https://github.com/friendsofgo/killgrave#create-an-imposter-using-json-schema If so, and still not enough. Can you share some examples about what do you...

Hi @eloo, Killgrave relies on [`gorilla/mux`](https://github.com/gorilla/mux) matcher to route requests. More specifically, it uses `HandleFunc(path string, f func(http.ResponseWriter, *http.Request))`, so based on [this StackOverflow thread](https://stackoverflow.com/questions/39754860/how-to-use-gorilla-mux-to-match-entire-path-with-regex), I guess it's not possible...