ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Mashenkov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4564) Ensure that builder approach is used for all setters in public API
Date Thu, 02 Feb 2017 13:06:51 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849890#comment-15849890
] 

Andrew Mashenkov commented on IGNITE-4564:
------------------------------------------

Done.

Another issues was found and I've send them to dev list [1].

[1] http://apache-ignite-developers.2346864.n4.nabble.com/Ensure-that-builder-approach-is-used-for-all-setters-in-public-API-td14222.html

> Ensure that builder approach is used for all setters in public API
> ------------------------------------------------------------------
>
>                 Key: IGNITE-4564
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4564
>             Project: Ignite
>          Issue Type: Task
>          Components: general
>    Affects Versions: 1.8
>            Reporter: Vladimir Ozerov
>            Assignee: Andrew Mashenkov
>             Fix For: 2.0
>
>
> *Problem*
> We employed "builder" approach for some configuration classes:
> {code}
> class Configuration {
>     Configuration setSomething(Something);
> }
> {code}
> This is very convenient for users. However, only part of our configs employ this approach.
> *Task*
> Let's make sure that all other parts of our API follow this rule.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message