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
It would be nice to have the initial layout in the inspector same as in the other views.
I am using the VScode extension heavily, and I saw that the layout is ported nicely to the Studio.
I know the positioning meta is a comment, but it is in the codebase :)
As the inspector is run in the codebase also, maybe you figure out a way to share this info trough to the inspector UI.
For starters, I am thinking at a simple implementation where we can supply the meta positioning string directly.
Another option I see is to point the inspector to the file that holds the meta and you can use the logic that is built into the Studio importer.
I am asking this because as we scale to over 10-20 states, one of the big advantages stately brings to the table is establishing a visual map of the flow.
Especially when developing, i see that the inspector brings a lot of value as I can just glance at it and I know what's what.
The text was updated successfully, but these errors were encountered:
It would be nice to have the initial layout in the inspector same as in the other views.
I am using the VScode extension heavily, and I saw that the layout is ported nicely to the Studio.
I know the positioning meta is a comment, but it is in the codebase :)
As the inspector is run in the codebase also, maybe you figure out a way to share this info trough to the inspector UI.
I am asking this because as we scale to over 10-20 states, one of the big advantages stately brings to the table is establishing a visual map of the flow.
Especially when developing, i see that the inspector brings a lot of value as I can just glance at it and I know what's what.
The text was updated successfully, but these errors were encountered: