Both Kotlin and Boot plugins are declared in the root module ?

yes, in

plugins {}

block with

apply(false)

Their versions are resolved through gradle.settings via

pluginManagement

, it could be related. Although in a toy project, which I created in attempt to illustrate the issue, this same approach still works correctly and resolves correct version.

Maybe that comes from

apply(false)

If that can help, the boot plugin does basically that:

Thanks for the pointer I'll look into it tomorrow

@sdeleuze you rock. this is super timely for me 😉

was just kicking off a new project after having not used this framework since pre-SB 2.0 and this helps me get started a lot more quickly. best part is you have tests that even go down in to jpa, very nice

@sdeleuze what’s the best way to give feedback on the tut? for example the compilerPlugins in the pom don’t parse in my repo (somehow the schema matching is different from your setup)

also would be interested if the community has a current lean/preference toward using TestNg vs junit 5, esp wrt spring apps and mockito mixed in

I am rewriting a java spring app into kotlin, but somehow the kotlin version doesn't pick up my application.yml

From what I can see, the code is the same as in java

The java version runs fine

Hope this is the right channel for this type of question. How do you handle the concept of optional fields in a REST API when using Kotlin? For my json output I am using data classes, for example like this:

data class User(val id: UUID, val username: String)

. I could add all possible fields (e.g.

friends

) to this class, but causes some problems: I now need to make sure Jackson ignores those fields if they were not requested, my fields now have to be nullable even when they really shouldn't be. Any ideas?

if i remember well jackson serialization allows for not outputing of null-valued fields let me check

ok, by default, only non-null fields are serialized

Yes, I can make it hide non-null fields. But sometimes a field is already nullable (say a

parent

), but if it's requested I still want it in the output, even if it's null.

i hope that may answer your question i’m not sure i understand it to be honest...

If client requests field

parent

to be returned, I need to return it, even if it's actually

null

(there might not be a parent).

ok then the above post will help you as it tells you how you can configure jackson to output

null

fields

No, the article shows how do it statically, I can say "ignore nulls" or "don't ignore nulls". But I need to have both, depending on whether or not a field was requested.

And even if I get that to work, this solution looks very ugly to me.

perhaps using a custom

JsonSerializer

then?

So now I need to write a custom serializer for every one of my json classes? How about no...

Why would you want to send a nulls field? Most clients will treat a field as null if it's not there unless they're deserializers are broken. Sounds like what you want to do is a bad API IMHO

In JS "not there" becomes

undefined

, not

null

. Also, how is it a bad API if I don't want random fields showing up or not based on their value? I want my JSON output to be consistent.

you could write a generic logic in your serializer i was just trying to help 🙂

(with not great results, i must admit)