KhrystynaPopadyuk commented on PR #2009: URL: https://github.com/apache/avro/pull/2009#issuecomment-1354061185
Hi @martin-g , Current PR does not update serialization/deserialization or other core avro functionality. It is only about classes that parse/map dotnet type to avro schema. Also, event though this changes can be user to quickly handle errors and add desired functionality, this is not the main purpose. Users/projects can have custom requirements that are not applicable for everyone and that should not be added to Apache.Avro. For example, at my project we use camel case naming convention for classes and properties (MyClass, MyProperty) for .NET, and there is requirement to use snake case naming for avro schemas across company (different languages) (my_class, my_property). Currently I use AvroField attribute to override property name. But this mean, each micro service should reefer to Apache.Avro and I should not forget to add that attribute to each property and not forget to update it when schema is changed (what happens often before release). After this PR I will be able to update property - field mapping to add implement custom requirements once. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
