-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overload method AbstractTreeViewer::internalConditionalExpandToLevel #2692
Open
fedejeanne
wants to merge
1
commit into
eclipse-platform:master
Choose a base branch
from
fedejeanne:AbstractTreeViewer_expand_condition
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this is to be a field that has a meaning across method calls, it should, e.g., be filled during intialization. If this value is only relevant during a call of
expandToLevel
(or other) method (and thus reinitialized in every call of that method), it should not be a field, as it is specific to the execution time of that method.You see the issues with this in the currently failing tests: there are other callers of
internalCustomizedExpandToLevel
, which accesses this field without it being initialized.So I see two options:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I initialized it in the constructor too to avoid NPEs.
The tricky part is passing it all the way down through the method calls until it reaches
internalCustomizedExpandToLevel
without adding an extra parameter (or overloading)internalExpandToLevel(Widget widget, int level)
. Which is why I was only able to support the use cases where the call comes throughexpandToLevel(...)
.Do you see any better way to do it? I couldn't come up with any.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This still means you are abusing a field of class to actually pass a method parameter. Fields of classes need to have a proper (or at least a reasonable) invariant they fulfill, but this one actually has not reasonable invariant (apart from "state x regarding last execution of y") as it is actually a method parameter.
I understand that changing the method signature is not easy/possible, but in my opinion solving this by abusing a field as a method parameter is an error prone design flaw. If you need to reinitialize the
shouldItemExpand
in some of the methods callinginternalCustomizedExpandToLevel
, why not in the others? Is there potentially some state in the predicate delivered bycreateShouldItemExpand
? Then that one will usually be invalid while executinginternalCustomizedExpandToLevel
without having it properly initialized.Wouldn't it be possible to achieve the same without any extension to AbstractTreeViewer by simply implementing the according subtype with an overwrittten
expandToLevel
, adding the predicate creation at the beginning of the method, and then consuming it in an overwrittensetExpanded
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consuming it in
setExpanded
won't work because the execution needs to be stopped in its consumer (internalCustomizedExpandToLevel
) which can only be achieved by changing its return value toboolean
(API change, since it's a protected method) and doing an early return.I've been looking at other subclasses of
AbstractTreeViewer
and I noticed that they end up hacking its way into the expansion mechanism by overriding methods. I think this may be a consequence of the little flexibility that the class offers. How about adding hook 2 methods that will be called only once right before and after the expansion runs? This would give the consumer/subclasses the chance to cleanly preserve some state outsideAbstractTreeViewer
and hopefully avoid future hacks.