[ 
https://issues.apache.org/jira/browse/AVRO-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Khrystyna Popadyuk updated AVRO-3603:
-------------------------------------
    Description: 
Current ReflectReader/Writer use a lot of static entities (classes, methods, 
fields). It is good to refactor them with interfaces and DI approach.
If do such update at once it requires massive changes and can we difficult to 
review and test.

This story is created as first step for such refactoring. It will include:
 - group classes by folders

 - rename (probably)

 - add IReflectService as main service to work with reflection

 - add DI

 - rename and refactor ClassCash and EnumCache (avoid method refactoring in 
scope of this story)

 

This is breaking changes.

 

 

  was:
Current ReflectReader/Writer use a lot of static entities (classes, methods, 
fields). It is good to refactor them with interfaces and DI approach.
If do such update at once it requires massive changes and can we difficult to 
review and test.

This story is created as first step for such refactoring. It will include:

- group classes by folders

- rename (probably)

- add IReflectService as main service to work with reflection

- add DI

- wrap ClassCash (avoid refactoring in scope of this story)

 

This is breaking changes.

 

 


> .NET/#C: Refactor ReflectReader/Writer: add IReflectService, rename and 
> refactor caches, add DI
> -----------------------------------------------------------------------------------------------
>
>                 Key: AVRO-3603
>                 URL: https://issues.apache.org/jira/browse/AVRO-3603
>             Project: Apache Avro
>          Issue Type: Improvement
>            Reporter: Khrystyna Popadyuk
>            Assignee: Khrystyna Popadyuk
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Current ReflectReader/Writer use a lot of static entities (classes, methods, 
> fields). It is good to refactor them with interfaces and DI approach.
> If do such update at once it requires massive changes and can we difficult to 
> review and test.
> This story is created as first step for such refactoring. It will include:
>  - group classes by folders
>  - rename (probably)
>  - add IReflectService as main service to work with reflection
>  - add DI
>  - rename and refactor ClassCash and EnumCache (avoid method refactoring in 
> scope of this story)
>  
> This is breaking changes.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to