Javier Antoniucci

It's very usefull to feed a mock server with input driven examples, please vote it!

Oh, yes! This is the way I am taking (see next raml example) but I am looking for a standardized one. ``` #%RAML 1.0 title: PoC on examples including inputs...

Absolutely! And all of you are doing an excellent work very appreciated by all of us. Thanks!

Yes, actually we are using the following annotation that is enough flexible to define uri, params, body and headers inputs. Nevertheless, I prefer a standard solution from the RAML specification....

done! available at https://github.com/jantoniucci/raml-spec-exampleInput This is a RAML spec proposal to optionally define the inputs that produces the example. These inputs could be uriParam, queryParam, header, body. The proposal is...

Sadly, I resolved this requirement using HAR ( https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/HAR/Overview.html) archives :( On Wed, 17 Oct 2018 at 11:49 Kanchan-Shagalolu wrote: > Hi Team, > > Any updates on the status...

yes, I'm agree, it is a good point of view have isolated data types. so, What about to have binding definitions at end-point's verbs? The goal is provide binding information...

It is still failing on 16-APR 

Me too. Are there any update nor workaround on it ? Thanks!

Yes, but it does not work with Bazel 1+ due to a deprecated rule (maven_jar) Are there plans to support open api generator ? They have more platforms supported like...