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
DROOLS-5067: Add Bound Fact Property checkmark #1314
Conversation
jenkins retest this please |
Thanks @jomarko , please do not forget to fix it also for /expression see: https://issues.redhat.com/secure/attachment/12465472/ExpressionTick.webm |
@jomarko @dupliaka I'm not totally convinced regarding this fix. I mean, when I implemented that tick, its scope was: the user manually selected that instance / property from test tools dock, which is different than highlight the instance / property in scope. With this change, the tick and the blue highlight will have the same meaning, and probably this is not the scope of that tick. |
@yesamer Ok, I see your point, I was not part of UX planning in the original jira, however still think this change makes more consistent behavior. For sure just my opinion, I propose to ask on weekly meeting where is broader audience. What do you think? |
@dupliaka ok, will incorporate also for expressions according to results of the discussion about this approach. |
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.
To be analyzed.
@dupliaka your requirement from #1314 (comment) should be incorporated now. |
jenkins execute full downstream build |
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.
@jomarko Fine for me, I only have a minor question
if (!listGroupItemView.isShown()) { | ||
onToggleRowExpansion(listGroupItemView, false); | ||
final ListGroupItemView instanceListGroupItemView = listGroupItemViewMap.get(factName); | ||
if (!instanceListGroupItemView.isShown()) { |
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.
@jomarko There is a particular reason about this rename?
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.
From my point of view listGroupItemView
just says what the variable is instance of, while instanceListGroupItemView
tries to provide more information, it is an ListGroupItemView
representing an Instance
, however if you think my rename is inapproprtiate I can revert it. Or if you have different proposal for name.
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.
@jomarko Thank you, fine for me.
@jomarko We have 2 failing tests, can you please check them? |
@Mock | ||
private FieldItemPresenter fieldItemPresenterMock; | ||
@Spy | ||
private FieldItemPresenter fieldItemPresenterSpy; |
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.
@jomarko @Spy
must be initialized, this is the reason of failing tests. (NPE is thown)
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.
Done
jenkins execute full downstream build |
1 similar comment
jenkins execute full downstream build |
jenkins execute full downstream build |
@dupliaka just friendly reminder, if you have a moment to review. |
jenkins execute full downstream build |
jenkins execute full downstream build |
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.
Could you please highlight the section in case if the field is an /expression?
@dupliaka done, please have a look |
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.
Looks fine, thanks!
@yesamer the code has changed slightly since your last review, not sure if you want to re-review or we can merge. |
jenkins please retest this |
@jomarko You can proceed. |
@yesamer thank you, once green will ask for merge. |
SonarCloud Quality Gate failed. 0 Bugs |
@kiegroup/gatekeepers could we please merge? |
@jomarko SonarCloud is reporting zero coverage.. but I see you have written tests; so merging. |
@manstis Unfortunetely test coverage is currently broken :/ |
For more details see: https://issues.redhat.com/browse/DROOLS-5067