apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vlad Rozov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (APEXCORE-674) Change access specifier of DTConfiguration.ValueEntry to private
Date Sun, 19 Mar 2017 16:12:41 GMT

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

Vlad Rozov updated APEXCORE-674:
    Remaining Estimate:     (was: 2h)
     Original Estimate:     (was: 2h)
              Priority: Trivial  (was: Major)
         Fix Version/s:     (was: 3.6.0)

DTConfiguration public methods suggest that ValueEntry class was initially not supposed to
be exposed to consumers of DTConfiguration and it (ValueEntry) encapsulated the internal implementation.

> Change access specifier of DTConfiguration.ValueEntry to private
> ----------------------------------------------------------------
>                 Key: APEXCORE-674
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-674
>             Project: Apache Apex Core
>          Issue Type: Sub-task
>            Reporter: Ajay Gupta
>            Assignee: Ajay Gupta
>            Priority: Trivial
> There is no need for ValueEntry class to be public. DTConfiguration provides methods
to access the member variables of ValueEntry class. Also, the setter functions set() and setInternal()
will be changed to return void instead of ValueEntry.

This message was sent by Atlassian JIRA

View raw message