You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 2, 2023. It is now read-only.
data class BusinessDaysModel(
val code: String,
val description: String,
val fromDate: LocalDate,
val fromDateIsBusinessDay: Boolean,
val nextBusinessDays: List<LocalDate>
)
would have generated a swagger with each of these properties being marked as required. I'm assuming this change is due to this PR #164 which correctly removes the originalRef stuff.
I'm not sure what the best way forward here, on the one hand I can fix this by annotating every class in my application with an @ApiModelProperty annotation (but this is awkward to keep in sync). Is there a way to hook into this perhaps using a model converter (i've never done this before...)? Or perhaps we can add kotlin support as a first class thing like scala?
The text was updated successfully, but these errors were encountered:
Hey, Kotlin/Scala support is only really on a best case efforts (as this was originally a quick plugin for a Java application). There are equivalent tests for Kotlin and Scala (although Scala is proving to be problematic at the moment). Unfortunately, I just don't have any time at the moment to really keep on top of this at the moment.
I agree though, annotating would be stupid (that's why Kotlin has "nullable" types!). There is also a lack of a test for this at all, so no wonder it's slipped through the net (not that I'm exactly happy with the level of testing here, but no time, no fix :( ).
It's worth pointing out that this probably also isn't working for Scala's and Java's Option types.
Previously a class like the below:
would have generated a swagger with each of these properties being marked as
required
. I'm assuming this change is due to this PR #164 which correctly removes theoriginalRef
stuff.I'm not sure what the best way forward here, on the one hand I can fix this by annotating every class in my application with an
@ApiModelProperty
annotation (but this is awkward to keep in sync). Is there a way to hook into this perhaps using a model converter (i've never done this before...)? Or perhaps we can add kotlin support as a first class thing like scala?The text was updated successfully, but these errors were encountered: