This version (2017/05/27 13:44) is a draft.
Approvals: 0/1

[09:56:04] * ChanServ sets mode: +o temporalfox [10:50:51] <aesteve> Hi everyone, hi pmlopes|Zzzz I was looking at!topic/vertx-dev/rU4FOhMBkFU (from swagger to code). And was curious to see if generation the other way around (from some kind of code to Swagger) was under the same GSoC project scope or another one ? [10:50:53] <aesteve> thanks [11:05:01] <slinkydeveloper> aesteve I'm going to work on this project, but i haven't planned it in my project. But i think that we can find a way to do it. I've read the git issue What's your idea of code → swagger? You are talking about generation at compile time or in runtime? [11:06:06] <aesteve> Hello slinkydeveloper good to see you're working on that project ;) [11:06:15] <aesteve> more compile time → swagger indeed [11:06:57] <aesteve> in fact I'm not sure if this is related to this GSoC project (I don't think so) or the “functional routing” one [11:07:06] <aesteve> that's why I was asking [11:07:27] <aesteve> anyway, happy to help you / test if you need, just ping me [11:07:59] <slinkydeveloper> It's not related to my project but I'm interested :) The real trouble of generation at compile time is: how do you describe request/response schemas? [11:08:27] <aesteve> we need a kind of wrapper (like the one you described) around Router [11:09:00] <aesteve> router.route(…).withIntParam(“test”).withBodyAs(Something.class).do(…) [11:09:10] <aesteve> (pseudo-code but you get the idea) [11:11:41] <slinkydeveloper> Okok understand. You think that If i project a “flexible” request validator for my project i think we can reach all the two results? [11:12:51] <slinkydeveloper> swagger → code : validator is compiled by routerfactory; code → swagger : validator is compiled by user [11:16:00] <slinkydeveloper> and then we need only a class that generate swagger from route objects. But I don't know how to reach this result in compile time. With java generators i can “read” all things attached to a route? [11:16:36] <aesteve> if it's generated at runtime actually it doesn't really matter [11:17:23] <aesteve> important thing is : it can be generated “on demand” either by a route itself (so that the doc is available for end users), or by a custom command, message over the event-bus, etc. whatever [11:18:37] <aesteve> yes I suppose the validator is common to both implementations, even if you shouldn't care for your project in the first place ;) we'll see that later [11:20:24] <slinkydeveloper> ok ok we can work on it without problems after gsoc [11:21:19] <slinkydeveloper> for now i will take care of writing a good validation class that allow all the two things [11:23:44] <aesteve> yes, focus on your project, don't want to confuse you with other stuff. Good luck !! [11:24:12] <slinkydeveloper> Thank you! [15:21:38] <aesteve> Did anyone find a way to indicate Success / Failure in a synchronous way ? [15:21:50] <aesteve> Something like SyncResult vs. AsyncResult [15:22:15] <aesteve> which means : something that can be either succeeded or fail with an exception, but immediately [21:10:35] * ChanServ sets mode: +o temporalfox

[22:29:07] *** ChanServ sets mode: +o temporalfox