You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we do not store activity function calls (CallActivity*) when code is used in a method that is not labeled a function. This is to prevent test code from being flagged. However, if an orchestrator calls another method where CallActivity* is used, the FunctionAnalyzer will not store these calls either.
This refactor would fix that case so that the FunctionAnalyzer would run on code of methods used inside an orchestrator function.
The text was updated successfully, but these errors were encountered:
Currently, we do not store activity function calls (CallActivity*) when code is used in a method that is not labeled a function. This is to prevent test code from being flagged. However, if an orchestrator calls another method where CallActivity* is used, the FunctionAnalyzer will not store these calls either.
This refactor would fix that case so that the FunctionAnalyzer would run on code of methods used inside an orchestrator function.
The text was updated successfully, but these errors were encountered: