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

Aleksandr Polovtsev updated IGNITE-17166:
-----------------------------------------
    Fix Version/s: 3.0
                       (was: 3.1)

> Simplify the configuration annotation processor
> -----------------------------------------------
>
>                 Key: IGNITE-17166
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17166
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Kirill Tkalenko
>            Assignee: Aleksandr Polovtsev
>            Priority: Major
>              Labels: iep-55, ignite-3, technical-debt
>             Fix For: 3.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> At the moment, the 
> *org.apache.ignite.internal.configuration.processor.Processor* looks 
> complicated due to the addition of internal, polymorphic and abstract 
> configuration, the code has become harder to read and edit.
> It is proposed to think about how and to divide this class into methods or 
> subclasses for each type of configuration.
> It would also be nice to write validation for class fields, for example that 
> a field (if not static) can only have one of the annotations *Value*, 
> *ConfigValue* and *NamedConfigValue*, etc.



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

Reply via email to