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
JBPM-8666: Stunner - Missing the ability to to specify the FEEL expressions #2768
Conversation
Can one of the admins verify this PR? Comment with 'ok to test' to start the build. |
ok to test |
@@ -171,7 +171,7 @@ The following assumes that the Standalone Showcase will be utilized. Some eviden | |||
10. Ensure that the *with JavaScript debugger* checkbox is **NOT** checked, as Chrome debugger will be used instead. | |||
11. Under *Before launch*, click the plus (+) sign. | |||
12. Select *Run Maven Goal*. | |||
13. Change the working directory to /[YOUR_DIR_LOCATION]/kie-wb-common/kie-wb-common-stunner/. | |||
13. Change the working directory to /[YOUR_DIR_LOCATION]/kie-wb-common/kie-wb-common-stunner/kie-wb-common-stunner-showcase/kie-wb-common-stunner-showcase-standalone/. |
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.
thanks for fixing this! 👍
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.
Hey @inodeman
Thanks for this, your first PR! :)
It looks good but a couple of comments:
- So is there no need to change the code for marshallers? is it un(marshalling) the expression type (feel) and its value properly? just asking to be sure, because if so, much better! hehe
- Missing tests for the changes. At least some test case should cover the new lines you added in both classes
Thanks!
can you please also update the ticket's title with the righ ticket id and description plz? |
@romartin I added the test you mentioned and also so that tests would not fail, can you review? |
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.
LGTM thanks.
Quick comment, if I don't remember wrong in master branch the trend is to use JBPM- prefixed tickets instead of "product" tickets like RHPAM-XXXX.
@romartin do this still apply?
jenkins retest this |
Jenkins execute full downstream build |
1 similar comment
Jenkins execute full downstream build |
Hi @romartin can you re-check this PR? thanks a bunch, it has been rebased and squashed into single commit |
jenkins execute full downstream build |
Check list
Code review
Acceptance Criteria
Found issues
Unrelated issues & future improvements
Used resourcesProcesses for quick test can be found here: https://github.com/bpmn-tutorials/FEELBPMN |
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.
Hi @inodeman,
looks and works good, thank you! Congratulations with your first contribution! :)
Thanks @inodeman , feel free now to close the ticket for this 👍 |
@romartin Can you review this PR, it is for the FEEL expression changes and the readme changes