search

appsmithorg / appsmith

Platform to build admin panels, internal tools, and dashboards. Integrates with 25+ databases and any API.
https://www.appsmith.com
Apache License 2.0
34.8k stars 3.77k forks source link

[Task] Remove browser run from Workflow debugging #35760

Open infinitetrooper opened 3 months ago

infinitetrooper commented 3 months ago
  1. Currently, executeWorkflow is run on Temporal and all other functions are run on the browser. This is confusing to the user as they see 2 experiences for 2 types of JS functions. We should remove the browser run altogether and support only running of the complete workflow on Temporal.
  2. So, the run button will only have the option of executeWorkflow function and run will run that on Temporal. No other JS object functions will be available to run.
  3. We should also remove the logs tab from the debugger along with this for the JS object as it is no longer useful without a browser run.

Acceptance Criteria:

  1. Workflow Execution on Temporal Only:

    • All workflows are executed exclusively on Temporal, with no browser execution support.
    • The executeWorkflow function is the only available option in the run button, executing solely on Temporal.

  2. No JS Object Functions in Run:

    • The run button should not display or allow any JS object functions to be executed apart from executeWorkflow.

  3. Removal of Logs Tab in Debugger:

    • The logs tab for JS objects is removed from the debugger as JS object browser runs are no longer supported.
ayushpahwa commented 3 months ago

Hey team! Please add your planning poker estimate with Zenhub @nsarupr @srix