Thorsten Hake

I started reading your various discussions on version 3 and I find it very refreshing that everything is discussed openly! The recordings of your meetings on youtube really help! I...

@magicmatatjahu thanks for your quick feedback! I took a liking to @smoya's statement in the 1st proposal in which he defined every server to be `remote` by default because in...

Thanks for the feedback, @dalelane! > That's an interesting idea. For a historical description of changes-until-now, you could just put them all in the AsyncAPI doc wrapped in a one-of...

Did you have a look at https://github.com/thake/avro4k-kafka-serializer? It provides a connection between Confluent Schema-Registry and Avro4k. Have a look at the discussion in #1 for more information.

@asmadsen, thanks for opening this PR! While this change would improve usability with default values in kotlin, I think it conflicts with how Avro schemas should be read. Avro schemas...

Currently avro4k only supports data classes as roots. But it should be possible to also support all other types. Do you want to give it a try and provide a...

@acruise thanks for raising this issue. Can you provide a small code (i.e. a failing unit test) so we can work on a solution more easily?

@ekerstens, thanks for raising this issue. I didn't have time to look into it yet, but I'll try to do so this week.

Any update on this? Apicurio added support for this with version 1.3 (see https://github.com/Apicurio/apicurio-registry/issues/642). Having this feature in the Confluent Schema registry would be really nice so that one can...

Additional to the use case of @hiddewie, an RFC3986 compliant ref resolving would also support an OpenAPI-Spec that is splitted in multiple (possibly remote) files.