Paulo Mateus

@bf4, it fixes https://github.com/zipmark/rspec_api_documentation/issues/407 In query parameters, the current regex parse wrong. For it, all the query is an unique parameter (see example in issue)

Is **mind** synonymous with **lying**? @bf4, I think there was some misunderstanding. Are you implying that I'm lying? Maybe my request has some side effect that I do not know....

@bf4 Ah, ok! I updated the description.

Hello @bf4, I add a test and fix other the case: * **url**: `/path/:param1/:param2?param3=:param3&param4=:param4` * **before**: `/path/{param1}/{param2?param3=:param3}&param4={param4}`. * **after**: `/path/{param1}/{param2}?param3={param3}&param4={param4}`.

> Oh, that looks straightforward enough. Any reason you didn't add a test? The reason was I have forgotten. At the last commit I added a test! :D

Proposed solution https://github.com/zipmark/rspec_api_documentation/blob/b65559c0af2ad50d2847d16966aab4a560a934b0/lib/rspec_api_documentation/writers/open_api_writer.rb#L240 to `super.gsub(/:(?[^\/|&]+)/, '{\k}')` http://regexr.com/3vmkq

Update status. I implemented an automatic generation of the diagram using the .yml generated by rspec_api_documentation. However the need for Issue still persists. The data is still useful for performing...

@jbyck, any news?

I could not: /

> It seems there are a couple bugs involved here with Autocomplete: > > 1. Regarding **not being able to focus/edit the Autocomplete field again once it has some text...