What problem are you trying to solve?
Hi! I have been recently using Weft, after having used Sim.ai and n8n, as its supposed to give more control and better debuggability for production based issues - for a developer along with helping go to production faster.

As you can see from the above image, the workflow is very simple but has actually become very complicated due to the number of variables that are clogging the screen. From my perspective, the variables there are just adding to the clutter and not providing any real feedback.
Proposed solution
My solution is to move these into an Inspect panel. I have taken up doing the changes and if this seems acceptable, I will raise a PR for the same.
Changes are:
- Variables are not shown as blocks.
- Inspect shows all variables by default.
- Upon clicking a block, it shows both the variables and the code associated with the block.
As per me, the above allows a clearer view, and easily able to go through the code. Below are few screenshots attached for the same.
Alternatives you considered
No alternatives were considered, as the above is the first proposal. Open for discussion.
How does this fit the design principles?
Mostly UI changes. Design principles align with backend fixes.
Seperate question, do these Python scripts run in a separate sandbox? Because I have been facing failures when the data being fetched is large. Is there a way to configure how these are executed, as well as the overall workflow timeout?
I have jumped here, because:
- Most web workflows fail when dealing with large inputs or outputs, or serialization, and they don't exactly give enough context about the errors to solve them.
Checks
What problem are you trying to solve?
Hi! I have been recently using Weft, after having used Sim.ai and n8n, as its supposed to give more control and better debuggability for production based issues - for a developer along with helping go to production faster.
Proposed solution
My solution is to move these into an Inspect panel. I have taken up doing the changes and if this seems acceptable, I will raise a PR for the same.
Changes are:
As per me, the above allows a clearer view, and easily able to go through the code. Below are few screenshots attached for the same.
Alternatives you considered
No alternatives were considered, as the above is the first proposal. Open for discussion.
How does this fit the design principles?
Mostly UI changes. Design principles align with backend fixes.
Seperate question, do these Python scripts run in a separate sandbox? Because I have been facing failures when the data being fetched is large. Is there a way to configure how these are executed, as well as the overall workflow timeout?
I have jumped here, because:
Checks