You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kie.apache.org by "elguardian (via GitHub)" <gi...@apache.org> on 2024/05/23 07:25:05 UTC

[I] EPIC - ReturnValueEvaluator [incubator-kie-issues]

elguardian opened a new issue, #1256:
URL: https://github.com/apache/incubator-kie-issues/issues/1256

   ReturnValueEvaluator in every place an expression that produces and outcome is required.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org


Re: [I] EPIC - ReturnValueEvaluator [incubator-kie-issues]

Posted by "elguardian (via GitHub)" <gi...@apache.org>.
elguardian commented on issue #1256:
URL: https://github.com/apache/incubator-kie-issues/issues/1256#issuecomment-2227855528

   @tiagobento This cannot be done in one go. (well it is feasible but the reviewer will go crazy)
   
   At present in every place the expression that produces some sort of value is done by different pieces of code. 
   1. This is not good for sustainbility and it is pretty error prone as any change in this part requires to change the logic everywhere. This lead to a situation where some of this expression are producing different outcomes depending where you execute. 
   2. This does not allow for writing how expressions work as you need to go one by one in every place how they work or how variables work.
   3. we cannot consolidate FEEL instead of MVEL as expression language (which is far better)
   
   Examples of this expression could be assignments, node input/output, conditions (nodes or boundary events), split/join node completion conditions. activation conditions, loops (multiinstandce) and so forth.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org