The to keyword is used to map a key to a value.Ī key value pair is also known as an entry. The key and value can be of different data type. The key should be unique and only one value can be stored for each unique key. Maps are used to store key and value pairs. If it's possible to properly convert a Map to either a JsonObject or JsonElement such as by using one of the many code snippets provided above, then this should be included in the library because it's a basic use case for many developers.In this tutorial we will discuss about Kotlin Map.due to this design decision, then this must be clearly stated in the README to prevent developers from running into such an issue. If rialization is unable to serialize Map, etc. I understand that there was an explicit (and useful) design decision to not use reflection.I thought it'd be trivial to serialize a Map because gson and jackson do it out of the box but apparently not. I only realized this after already spending ~2 days migrating nearly a thousand lines of serialization code, and now I've rolled back to using jackson instead. I'm using the graphql-java library which returns a Map (i.e., Map), and I'm unable to figure out how to properly convert this into a JsonObject or JsonElement which means it's impossible for me to use rialization. Guess you could use reflections to iterate over all fields but wouldn't that be overkill?
*obviously it will only work with primitives and maps/arrays of primitives - if you attempt to serialize/deserialize complex objects it won't work. Override fun serialize(encoder: Encoder, value: Any) Override val descriptor: SerialDescriptor = buildClassSerialDescriptor("Any")
If anyone is looking for generic Map serialization based on some preliminary testing this seems to work for me class Generic(
0 kommentar(er)
