Closed thomas-melville closed 6 years ago
Hi,
I started digging into the code and I see there is a check on this line whether to add the name field to the annotation of not. I'm not sure what the values mean so I will dig into it again tomorrow.
Hi,
We got to the bottom of it. The type definition in the raml began with a lower case letter, when we changed it to start with an uppercase letter it added the name field to the RequestParam annotation. From reading the RAML spec all type declarations starts with an upper case letter so the fault is with me.
Hi,
I'm using your plugin to generate the interface for our controller, thank you very much. There is one thing I see which isn't being generated, the name field in the RequestParam annotation for a MultiPartFile.
I can take an existing unit test as an example. RAML: https://github.com/phoenixnap/springmvc-raml-plugin/blob/466f96e4d2661c6df26b08d48c5d5298992fd0a2/src/test/resources/ramls/test-multipart-mime-request.raml Unit Test: https://github.com/phoenixnap/springmvc-raml-plugin/blob/466f96e4d2661c6df26b08d48c5d5298992fd0a2/src/test/java/com/phoenixnap/oss/ramlplugin/raml2code/rules/MultipartMimeRequestTest.java Validation: https://github.com/phoenixnap/springmvc-raml-plugin/blob/466f96e4d2661c6df26b08d48c5d5298992fd0a2/src/test/resources/validations/MultipartRequestStub.java.txt
The generated code is:
Whereas I would like it to be:
in my interface
Is this intentional, a missed impact or a bug?