Chuckame

New features: - Handle any primitive value and `@Contextual` as map keys #114 Breaking changes: - `@AvroInline` removed as it is replaced by kotlin's value classes - Stop supporting `@AvroFixed`...

## Issue Currently, we are only able of encoding and decoding records as root, but we cannot encode and decode primitive values, arrays, or maps. ## Proposal Be able of...

Beautify the Avro api entrypoint

2

Currently, to do common stuff, we have to start by `Avro.default`. But when we want to override defaults, we do like this: ```kotlin Avro(SerializersModule { contextual(...) }, AvroConfiguration( namingStrategy =...

## Issue We currently have a `LocalDate` field with the `LocalDateSerializer`. Now if we use `Json` or any other decoder/encoder, it fails as the serializer is only accepting an avro...

See #182 and #183 for replacements

- Separate naming strategies (#178) - remove AvroName[space] and add AvroNamespaceOverride (#165)

## Bug fixes - ✅ #166 ## Improvements - Revamp the `Avro` entrypoint completely to reduce the complexity and improve extensibility. Example: [Json class in kotlinx serialization](https://github.com/Kotlin/kotlinx.serialization/blob/master/formats/json/commonMain/src/kotlinx/serialization/json/Json.kt). See #163 -...

Currently, annotating classes is totally open to mistakes, while they are just silently ignored when not appliable. Let's take the following example. We can annotate a field with `AvroFixed` even...

Remove AvroName and AvroNamespace in favour of native SerialName

6

Now, to redefine record's name or namespace, just use `@SerialName("RecordName")` or `@SerialName("a.good.namespace.RecordName")` (note that **record name is now explicit**). The goal of kotlinx serialization framework is to be a declarative...

Value classes not working (feature request ?)

4

Hey, Is there a way to have value classes ? (previously called inlined classes) The goal is to wrap primitive types (string, int, in our example) inside a value class,...