zigzago

reproduced with 2.13.4 ;)

I would say this is more a kotlinx.serialization question (see https://github.com/Kotlin/kotlinx.serialization/issues/33). I think it's not feasible for now.

No, the issue is only with `@SerialName,` because KMongo needs to check the property name in order to build dedicated path for mongo queries (and also apply custom behaviour for...

@dwlizlo the -tests modules are not in a /test test source folder because they need to be launched by more than one module. For example, `kmongo-core-tests` tests are used by...

all sub modules are here: https://github.com/Litote/kmongo/blob/master/pom.xml#L31 - kmongo uses kmongo-core (mongo sync driver extensions) & kmongo-jackson-mapping dependencies - kmongo-native uses kmongo-core & kmongo-native-mapping - kmongo-serialization uses kmongo-core & kmongo-serialization-mapping -...

I will implement it for 4.3.0

You are right, UUID is not supported for now as id type

I change the title of the issue. What is not supported is Id implementation with UUID (related to "unsupported id type" error message). Direct UUID _id type declaration is supported.

You are right, the KMongo `ensureIndex` extension has not the same goal than old mongo method `ensureIndex`. So it does not follow the mongo spec. In fact, it was designed...

`createOrRebuildIndex` looks good to me. A PR would be welcome :)