Releases: phoenixnap/springmvc-raml-plugin
Releases · phoenixnap/springmvc-raml-plugin
v2.0.5
v2.0.4
Improvements:
- #152 Collision with java keywords
- #254 Skip headers in method parameters when using
injectHttpHeadersParameter
- #257 Support for
DeferredResult
- #282 Enums create
String.java
source file which is confusing
Bugfixes
- #266 Collections are always initialized
- #275 Import Statement for BigDecimal/BigInteger not generated for responses
- #281
Spring4ControllerStubRule
omitsResponseEntity
for POJOs (data types) - #284
FeignClient
issues - #286
overrideNamingLogicWith
not respected when generating rest client - #288 Import Statement for BigDecimal/BigInteger not generated for request body
Other Changes
raml-parser-2
updated to1.0.26
README.md
got link to PhoenixNAP blog post on using RAML to document API contracts
v2.0.3
v2.0.2
v2.0.1
2.0.0
Removed support for:
- RAML 0.8
- Spring 3
- RAML creation (we're focused on the contract-first approach)
- Keeping code and RAML in sync
Improvements:
Bugfixes
- #235 Delete does not generate body parameter
- #236 Generated client sends query param even if the value is null
Other changes:
- Project is restructured. Also, packages changed and new rules' package is
com.phoenixnap.oss.ramlplugin.raml2code.rules
so new configuration might look like this:
<configuration>
<ramlPath>src/main/resources/public/api.raml</ramlPath>
<outputRelativePath>target/generated-raml-mvc</outputRelativePath>
...
<rule>com.phoenixnap.oss.ramlplugin.raml2code.rules.Spring4ControllerDecoratorRule</rule>
<generationConfig>
<useCommonsLang3>true</useCommonsLang3>
<includeConstructors>true</includeConstructors>
<generateBuilders>true</generateBuilders>
</generationConfig>
</configuration>
- Method naming logic is changed. Previously, methos names were generated based on resource path and now based on request/response objects and parameters.