Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Execution Flow Rework #252

Closed
FabienRoger opened this issue Feb 9, 2022 · 0 comments · Fixed by #255 or #249
Closed

Execution Flow Rework #252

FabienRoger opened this issue Feb 9, 2022 · 0 comments · Fixed by #255 or #249
Labels
enhancement New feature or request

Comments

@FabienRoger
Copy link
Contributor

FabienRoger commented Feb 9, 2022 •
edited
Loading

Refactor the execution flow so that each block is responsible for its own execution, so that closed sockets don't trigger execution.

Edit: I feel a full rework of this is not worth doing for now, without a clear vision of how the flow should work later, so the linked PR looks more like small improvements than a full rework.
@FabienRoger FabienRoger added the enhancement New feature or request label Feb 9, 2022
This was referenced Feb 9, 2022
Closed
Merged
This was linked to pull requests Feb 10, 2022
🎉 Make execution flow ignore off-sockets #255
Merged
Create a new add socket button #249
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
1 participant
@FabienRoger