Remove the `value` output param from Lambda Invoke activity · TIBCOSoftware/flogo#410

(0 留言) (0 反應) (0 負責人)CSS (2,348 star) (290 fork)batch import

good first issuekind/enhancement

描述

Current behavior (how does the issue manifest): The lambda invoke activity returns a value object which includes the payload and the []byte serialized response. This really has no real purpose and causes confusion between the unmarshaled payload in the return param result .

Expected behavior: Remove the value param, as both the unmarshaled payload and the status are both returned in separate params already, no need to keep a struct of the raw return data.

Minimal steps to reproduce the problem (not required if feature enhancement):

Please tell us about your environment (Operating system, docker version, browser & web ui version, etc):

Flogo version (CLI & contrib/lib. If unknown, leave empty or state unknown): 0.X.X

Additional information you deem important (e.g. issue happens only occasionally):

貢獻者指南

技術棧: go
領域: backendcloud
議題類型: refactor
難度: 2
預計時間: 1-3 hours
活動狀態: stale
清晰度: clear
前置要求: Go programmingFlogo activity conceptsAWS Lambda invoke basics
新手友善度: 60
研究方向: Locate the Lambda Invoke activity source code in the Flogo repository, typically under /contrib/activity/lambda. Identify where the `value` output parameter is defined, likely in the activity's metadata or result struct. Remove this parameter and update any references to it in the activity implementation. Ensure that the `result` parameter and status are still correctly returned. Since there are no comments or linked PRs, review the current code for any downstream dependencies on `value`. No tests are mentioned, but verify that the change does not break existing functionality.