Romain Leroux

Actually there is [yaml-pro](https://github.com/zkry/yaml-pro/) that achieves similar results using treesit in the functions `yaml-pro-ts-indent-subtree` and `yaml-pro-ts-unindent-subtree`.

What would be the benefit of such a setup ? Right now this crate is updated when a new version of `apache-avro` is published.

This logic was implemented for apache-avro 0.17 using a dedicated branch until it was released. The same strategy will be used for future apache-avro versions, on an as-needed basis.

Hello, Thank you for bringing the `"protocol"` type to my attention. However I feel that the `Protocol` struct is something that should be living in [apache-avro](https://crates.io/crates/apache-avro) as it's part of...

Hello, I have actually opened an issue on their Jira: https://issues.apache.org/jira/browse/AVRO-3928 As far as I know @martin-g fixed it already, now we just have to wait for a new release...

I have tried to test it by updating `Cargo.toml` as follows: ```toml [dependencies] apache-avro = { version = "0.17", features = ["derive"] } [patch.crates-io] apache-avro = { git = "https://github.com/apache/avro.git"...

Giving it a quick try, it looks like `BigDecimal` is not re-exported as part of the public API (contrarily to say `apache_avro::Duration`) , I think it should be re-exported so...

@martin-g If `BigDecimal` gets re-exposed through `apache_avro::BigDecimal` then everything should be fine. For now I have pushed my fixes to the branch [apache-avro-0.17](https://github.com/lerouxrgd/rsgen-avro/tree/apache-avro-0.17), I will merge it into master when...

By the way, I think that the timestamp fields should be defined as: ```json { "name": "timestamp", "type": [ "null", {"type": "long", "logicalType": "timestamp-millis"} ], "doc": "Optional UNIX Epoch time...

I am trying with the following schema: ```json { "type": "record", "name": "Decimals", "fields": [ { "name": "a_decimal", "type": {"type": "bytes", "logicalType": "decimal", "precision": 4, "scale": 2} }, { "name":...