I appreciate it 🙂 I just want to keep this as type-safe as possible

understood... but since i never had this issue i cannot help more than trying to google it

One thing I have come up with is having a separate class per field:

interface UserField
data class User(val id: UUID, val name: String, val fields: List<UserField>)
data class UserBirthday(val birthday: LocalDate) : UserField

Thoughts?

want my honest opinion?

That's why I am asking, but I can imagine what it's going to be 😄

That’s why I am asking

i prefer to make sure cultural gap and all so here it is: to me, it feels like over-engineering i’m a “keep it simple and stupid”-kind of guy so custom serializer is good enough

A custom serializer is a PITA to write though 😄

ok but it has 2 advantages: 1. you write it once 2. it’s nicely decoupled from the rest of your code

I'll try and give it a shot. Not sure how I'll get hold of the request parameters in the jackson serializer though (is that really decoupled?).

If you're consistent about not sending values if an element is null, I still don't see an issue. Your JS clients will learn to look for undefined. Your Android clients will treat it as null. Your iOS clients will also treat it as missing. Consistency is what API consumers want IMHO

If you're sending fields with a value of null, you're just wasting bandwidth for Android users at least 🙂

I highly disagree with your view here.

yep...as I do w/ yours...wanted to see your justification

keep it civil guys 🕊️

Wasn't fighting...mostly curious 🙂

so true story...our backend at one point sent fields that are null in our REST API responses but then at some point took that out. It was inconsistent which APIs did what....depending on who configured which API. When they finally took out the null fields from the responses, web/iOS blew up of course because they treated the dictionaries as tri-state.... exists/null/missing. And on the Android side, we were using a streaming deserializer which was dependent on the order of fields 🤦‍♂️ . Yes, you can imagine the carnage when this change happened 😞 Luckily we could version the APIs and config for this...but consistency is important IMHO...

Is this thing recorded on KT bug tracker: https://blog.jetbrains.com/kotlin/2018/04/kotlin-1-2-40-is-out/#comment-45597 ? We've just encountered this issue when upgrading to 1.2.40

try to use 1.2.41 it has some fixes

oh, I see here https://youtrack.jetbrains.com/issue/KT-23973

yes, I encountered this issue also

can someone confirm that for 2.0.2 the @Service annotation is still in use for classes?

getting a service that is not registering as a bean and failing autowiring in a test

hi all ! I would like to refactor this code by avoiding re assigning the variable spec. I feel that this is not well design imperative programming style nor functional.

anyone know of a good breakdown for when to use the annotation s @ExtendWith and @SpringBootTest by chance? in particular I want to run some unit tests for a service via injection and not have it run my application beans. To get it to run, I have to use both annotations, but then it runs my app beans and I don’t want that

would be great if there was a article/demo repo that had unit and integration tests for 1. mvc [a) controllers, b) services, c) repositories], 2. uses a separate deployment and test config; 3. uses h2 for test, and postgres for runtime; 4. and initializes each db uniquely

purpose, navigating all the plethora of annotation changes, best practices, config stuff, etc. kind of painful right now lol

@michael salmon http://www.baeldung.com/spring-boot-testing, especially chapter 5

Please vote for https://youtrack.jetbrains.com/issue/KT-23834 if you care about

WebTestClient

being usable with Kotlin

BTW

spring-kotlin-functional

has been updated to use it, see https://github.com/sdeleuze/spring-kotlin-functional/blob/master/src/test/kotlin/functional/IntegrationTests.kt for standalone and https://github.com/sdeleuze/spring-kotlin-functional/blob/boot/src/test/kotlin/functional/IntegrationTests.kt for Boot version.

@sdeleuze anyway to use kotlin bean dsl with

@Scheduled

annotation? in other words, does the

beans().initialize()

method kick-off any annotation scan? how do you pass dependencies in your

bean()

methods if they are not bean dependency?