- [#625] How do I specify api version? bug
- [#623] @ApiImplicitParam always adds enums in json in version 1.0.1 bug
- [#617] Java codegen - generates class name Void.java bug
- [#618] Ranges are treated like enums bug
- [#522] @Unwrapped types have problems sometimes... bug
- [#482] Custom ObjectMapper not recognized by swagger-springmvc bug
- [#593] Container types in model properties are now rendered as "arrays"
- [#589] Add support for @RequestPart annotation
- [#560] Having a model property of type Class doesn't work as expected
- [#554] @ApiModelProperty "hidden" attribute has no effect
-
[#552] Enable ApiResponses annotation on interface
-
[#541] Fix the rendering of enums in model properties. Attempt to clean up logic to handle bare enums in the response
-
[#539] Prevents excludeAnnotations from modifying the defaults in SpringSwaggerConfig
-
[#496] Upgerades swagger-ui webjar version. Adds jstl dependencies to fix webjar context path
-
Use @ApiModel.value as alternate type name for serialization
-
Respect original property ordering on models.
-
Introduced pmd and addressed the violations and added findbugs plugin
-
This solution lets delegates the choice of interpreting the position. Part of the solution to the problem reported in #519
- Removed all transitive dependencies on swagger-core and scala which reduces dependency size by ~30Mb
- Provided default model substitutes for spring's ResponseEntity and HttpEntity
- Upgraded to Jackson 2.4.4
- Fixed an issue where 'body' parameters were not being named as 'body'
- Ability to disable default response messages
springfox.swagger.plugins.SwaggerSpringMvcPlugin .useDefaultResponseMessages
- All dependencies on swagger-core's scala models (
com.wordnik.swagger.model
) have been removed. The equivalent java models now live inspringfox.swagger.models.dto
. If an application has configured swagger auth or custom response messages it's likely there will be compilation issues with this upgrade, the fix is to simply import the java equivalents fromspringfox.swagger.models.dto
. There are also builders inspringfox.swagger.models.dto.builder
. These are the most likely offenders:- com.wordnik.swagger.model.ApiInfo
- com.wordnik.swagger.model.Authorization
- com.wordnik.swagger.model.AuthorizationCodeGrant
- com.wordnik.swagger.model.AuthorizationScope
- com.wordnik.swagger.model.AuthorizationType
- com.wordnik.swagger.model.GrantType
- com.wordnik.swagger.model.ImplicitGrant
- com.wordnik.swagger.model.LoginEndpoint
- com.wordnik.swagger.model.OAuth
- com.wordnik.swagger.model.OAuthBuilder
- com.wordnik.swagger.model.TokenEndpoint
- com.wordnik.swagger.model.TokenRequestEndpoint
- com.wordnik.swagger.model.ResponseMessage
- 8294504b1b867d39d66e5ef69306c245c1496161 Adding the posibility of ignoring an entire controller
- Ingoring all methods of a controller by adding an excluded annotation on class level
- @ApiIgnore can now be specified on Type, but also on Parameter and has been added to the defaultIgnorableParameterTypes Set
- Allows detection of customs SwaggerSpringMvcPlugins from spring context's with ancestors.
- Fixed an issue with the ClassOrApiAnnotationResourceGrouping that was making a cases sensitive compare
- Autowired the ObjectMapper ...
- Made junit a test dependency
- Merge pull request #260 from MinosPong/master
- Updating the notable dependencies
- Merge remote-tracking branch 'upstream/master'
- Fix Enum allowable list does not display in the Swagger Model
- Updated the version dependencies
- Merge pull request #246 from jkorri/allowables_for_enum_array_params
- Fixed the tests as a result of fixing #255
- Removes the duplication of controller naming strategy being set
- Fix the rendering of void responses
- Merge pull request #258 from lucastschmidt/master
- #257 bug - slow scanner
- When substituting types the base types should not be included as models
- Include array element type for method parameters
- Automatically retrieve allowableValues and set allowMultiple for enum arrays
- Update readme.md
- Released version 0.8.3
- [maven-release-plugin] prepare for next development iteration