Hello everyone after updating to Kotlin 1 4 10 with Serializ | Serialization | Kotlinlang

Join the conversation Join Slack

Channels

# 100daysofcode

# 100daysofkotlin

# 100daysofkotlin-2021

# advent-of-code

# algolialibraries

# android-architecture

# android-databinding

# android-studio

# androidgithubprojects

# androidthings

# androidx-xprocessing

# announcements

# apollo-kotlin

# arksemdevteam

# arrow-contributors

# awesome-kotlin

# beepiz-libraries

# cincinnati-user-group

# code-coverage

# codemash-precompiler

# codingconventions

# collaborations

# competitive-programming

# competitivecoding

# compose-desktop

# compose-hiring

# compose-ui-showcase

# connect-audit-events

# cscenter-course-2016

# docs-revamped

# domain-driven-design

# effective-kotlin

# effectivekotlin

# embedded-kotlin

# event21-community-content

# fb-internal-demo

# fluid-libraries

# general-advice

# getting-started

# github-actions-kotlin-dsl

# graphql-kotlin

# graviton-browser

# hazelcast-explorer

# image-processing

# intellij-plugins

# intellij-tricks

# introduce-yourself

# istanbulcoders

# jackson-kotlin

# java-to-kotlin-refactoring

# javadevelopers

# jhipster-kotlin

# jobsworldwide

# juul-libraries

# jvm-ir-backend-feedback

# k2-early-adopters

# kampkit-support

# kgen-doc-tools

# kloudformation

# kotest-contributors

# kotlin-by-example

# kotlin-data-storage

# kotlin-in-action

# kotlin-inject

# kotlin-logging

# kotlin-mumbai

# kotlin-native

# kotlin-pakistan

# kotlin-plugin

# kotlin-roadmap

# kotlin-samples

# kotlin-serbia

# kotlin-szeged

# kotlin-website

# kotlinacademy

# kotlinforbeginners

# kotlingforbeginners

# kotlinprogrammers

# kotlintest-devs

# kotlinultimatechallenge

# kotlinx-datetime

# kotlinx-files

# lambdaworld_cadiz

# language-evolution

# language-proposals

# leedskotlinusergroup

# lets-have-fun

# library-development

# machinelearningbawas

# metro-detroit

# monsterpuzzle

# multiplatform

# myndocs-oauth2-server

# navigation-architecture-component

# ohio-kotlin-users

# package-search

# pattern-matching

# pocketgitclient

# practical-functional-programming

# prozis-android-backup

# python-contributors

# realworldkotlin

# refactoring-to-kotlin

# refreshversions

# russian-kotlinasfirst

# serialization

# sg-user-group

# skia-wasm-interop-temp

# sofl-user-group

# spotify-mobius

# spring-security

# squarelibraries

# stackoverflow

# stayhungrystayfoolish

# strife-discord-lib

# swagger-gradle-codegen

# swiss-user-group

# talking-kotlin

# tricity-kotlin-user-group

Powered by Linen

Channels

zeugederunity

zeugederunity

2 years ago

Hello everyone, after updating to Kotlin 1.4.10 with Serialization 1.0.0-RC I realized, that the

SerialName

annotation was set to

retention(BINARY)

Is there any way in Kotlin 1.4.x with Serialization 1.0.0-RC to retrieve the

SerialName

of an annotated property? Because reflection is now not possible anymore.

Vsevolod Tolstopyatov [JB]

Vsevolod Tolstopyatov [JB]

2 years ago

Could you please file an issue and explain your use-case? Specifically, could you please elaborate on why do you want to inspect properties reflectively instead of using

SerialDescriptor

?

zeugederunity

zeugederunity

2 years ago

I am using the Kotlin-Serializer for a MongoDB binding (with KBson and some additional modifications like a shared commons etc.) For improvint the writing of queries i wrote a little DSL, therefore i have functions like this:

inline infix fun <T : Any, TItem> KProperty1<T, TItem>.eq(value: TItem?): Bson = fieldName eq value

Usually using the default name reflection of a dataclass-property is enouth, bus due to some legacy code and naming conventions i have to use

@SerialName

for some properties like

@SerialName("_id") val id: Id<CompanyData>

. In 1.3.70 i was able to retrieve the reflected name of the KProperty of a class by this:

annotations.filterIsInstance<SerialName>().singleOrNull()?.name ?: name

and then cache it. My workaround at this point is, that i wrote a second annotation class

@Retention(AnnotationRetention.RUNTIME)
@Target(AnnotationTarget.PROPERTY)
annotation class MongoDBName(val name: String)

and use this class to reflect the name. Sadly this has the sideeffect, that my properties look like this

@SerialName("_id") @MongoDBName("_id") val id: Id<CompanyData>

which is quite inconvenient and harder to maintain.

I'll write a proper issue report tomorrow, it's it is already quite late. Thank you for the reply, good night.

Wrote a Feature Report:https://github.com/Kotlin/kotlinx.serialization/issues/1081

View count: 2

Join thread in Slack