[
https://issues.apache.org/jira/browse/IGNITE-24803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-24803:
---------------------------------------
Description:
IgniteToStringBuilder automatically finds fields it will use to build object's
string representation; reflection is used to find them. When doing so, only
private fields are considered; fields of other access levels are skipped.
This causes troubles: sometimes we need to make a field protected. When we do
so, we make it disappear from the toString() representation, and we usually
miss this.
The code was ported from Apache Ignite 2, and nobody of the active developers
was able to recall any good reason for this behavior. It seems that it's some
artifact of the past, so we can just change it to work in a more obvious way.
> Do not skip non-private fields in IgniteToStringBuilder
> -------------------------------------------------------
>
> Key: IGNITE-24803
> URL: https://issues.apache.org/jira/browse/IGNITE-24803
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> IgniteToStringBuilder automatically finds fields it will use to build
> object's string representation; reflection is used to find them. When doing
> so, only private fields are considered; fields of other access levels are
> skipped.
> This causes troubles: sometimes we need to make a field protected. When we do
> so, we make it disappear from the toString() representation, and we usually
> miss this.
> The code was ported from Apache Ignite 2, and nobody of the active developers
> was able to recall any good reason for this behavior. It seems that it's some
> artifact of the past, so we can just change it to work in a more obvious way.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
