<https://lh3.googleusercontent.com/-ZtaGVEz5pCk/WHhbvo-t88I/AAAAAAAAAAQ/8fyjFlckxosynZDUJ4LSOLsatkCtJexdgCLcB/s1600/code.png> <https://lh3.googleusercontent.com/-CQOM_rp-a5g/WHhb6u1RqlI/AAAAAAAAAAY/KiYGqvFwQuAtwNk7m4csL4mwotc1KxsOACLcB/s1600/swagger1.png> <https://lh3.googleusercontent.com/-GAd4oVZZPl8/WHhb-r2kPSI/AAAAAAAAAAc/-umU1G2k5Vs-dsNt9kKubGLSR8WLXqg7QCLcB/s1600/swagger2.png>
Hello, I'm trying to utilize @PathVariable binding within my @RequestMapping method while also preserving Swagger UI's capability to input each path variable in a separate input box. For example, if I have the above code (pic 1) it produces the above Swagger page (pic 2+3) which is fantastic, but you can see that the Args Object is just a json block (pic 2) when I was hoping it would unwrap into the full args as in (pic 3). Is there any configuration value I can set up or annotation I can use to mark the behavior I'd like? Or even any thoughts on how to extend Swagger to do so? Thank you so much for your time, Kevin -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
