Skip to content
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

Merged
merged 5 commits into from Mar 4, 2020

Conversation

jomarko
Copy link

@jomarko jomarko commented Feb 13, 2020

@yesamer
Copy link
Member

yesamer commented Feb 13, 2020

jenkins retest this please

@dupliaka
Copy link
Member

Thanks @jomarko , please do not forget to fix it also for /expression see: https://issues.redhat.com/secure/attachment/12465472/ExpressionTick.webm

@yesamer
Copy link
Member

yesamer commented Feb 14, 2020

@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.

@jomarko
Copy link
Author

jomarko commented Feb 14, 2020

@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?

@jomarko
Copy link
Author

jomarko commented Feb 14, 2020

@dupliaka ok, will incorporate also for expressions according to results of the discussion about this approach.

@yesamer
Copy link
Member

yesamer commented Feb 14, 2020

@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?

@jomarko It sounds good :)

Copy link
Member

@yesamer yesamer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be analyzed.

@jomarko
Copy link
Author

jomarko commented Feb 26, 2020

@dupliaka your requirement from #1314 (comment) should be incorporated now.

@jomarko
Copy link
Author

jomarko commented Feb 26, 2020

jenkins execute full downstream build

Copy link
Member

@yesamer yesamer left a 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()) {
Copy link
Member

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?

Copy link
Author

@jomarko jomarko Feb 27, 2020

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.

Copy link
Member

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.

@yesamer
Copy link
Member

yesamer commented Feb 26, 2020

@jomarko We have 2 failing tests, can you please check them?

@Mock
private FieldItemPresenter fieldItemPresenterMock;
@Spy
private FieldItemPresenter fieldItemPresenterSpy;
Copy link
Member

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)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@jomarko
Copy link
Author

jomarko commented Feb 27, 2020

jenkins execute full downstream build

1 similar comment
@jomarko
Copy link
Author

jomarko commented Feb 27, 2020

jenkins execute full downstream build

@jomarko
Copy link
Author

jomarko commented Feb 28, 2020

jenkins execute full downstream build

@jomarko
Copy link
Author

jomarko commented Mar 2, 2020

@dupliaka just friendly reminder, if you have a moment to review.

@jomarko
Copy link
Author

jomarko commented Mar 2, 2020

jenkins execute full downstream build

@jomarko
Copy link
Author

jomarko commented Mar 3, 2020

jenkins execute full downstream build

Copy link
Member

@dupliaka dupliaka left a 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?

@jomarko
Copy link
Author

jomarko commented Mar 3, 2020

@dupliaka done, please have a look

Copy link
Member

@dupliaka dupliaka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine, thanks!

@jomarko
Copy link
Author

jomarko commented Mar 4, 2020

@yesamer the code has changed slightly since your last review, not sure if you want to re-review or we can merge.

@jomarko
Copy link
Author

jomarko commented Mar 4, 2020

jenkins please retest this

@yesamer
Copy link
Member

yesamer commented Mar 4, 2020

@jomarko You can proceed.

@jomarko
Copy link
Author

jomarko commented Mar 4, 2020

@yesamer thank you, once green will ask for merge.

@sonarcloud
Copy link

sonarcloud bot commented Mar 4, 2020

SonarCloud Quality Gate failed.

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

0.0% 0.0% Coverage
0.0% 0.0% Duplication

@jomarko
Copy link
Author

jomarko commented Mar 4, 2020

@kiegroup/gatekeepers could we please merge?

@manstis
Copy link
Member

manstis commented Mar 4, 2020

@jomarko SonarCloud is reporting zero coverage.. but I see you have written tests; so merging.

@manstis manstis merged commit 636c537 into kiegroup:master Mar 4, 2020
@yesamer
Copy link
Member

yesamer commented Mar 4, 2020

@manstis Unfortunetely test coverage is currently broken :/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants