Is there a way to remember the collapsed state of components after deploy?

1

This topic was automatically generated from Slack. You can find the original thread here.

Raymond Camden : I’m sure there’s a bug for this, but are you going to fix “remembering the state of code collapse” for steps? Ive got a workflow where step 2 just defines a big ass array. i collapse it as it’s noise essentially. as im debugging this workflow, its kinda randomly re-opening as i load new executions

2

Raymond Camden : not random, as i execute the workflow, every new one has it opened. id love it such that if i close it once, it stays closed

3

Dylan Sather (Pipedream) : in fact, there’s an issue that you raised! [BUG] Deploy resets view settings on individual steps · Issue #809 · PipedreamHQ/pipedream · GitHub

4

Raymond Camden : hah!

5

Dylan Sather (Pipedream) : I’m discussing with the team again

6

Dylan Sather (Pipedream) : I’m attaching the new builder label to this one too because it focuses you on a single step at a time, and I think it may address the core use case. The code / output of all prior steps is collapses by default as you work on a new step. When we release the beta, see what you think