Design and implement the Start block, ensuring it triggers workflows.

[c0rtexR]

Subtask: Design and implement the Start block, ensuring it triggers workflows.

Task Overview: Develop the Start block that initializes workflows in the data-river system. This block will be responsible for triggering the execution of a workflow and passing any initial data or parameters to subsequent blocks.

Specific 🎯:

• Design the Start block to serve as the entry point of the workflow, ensuring it can trigger the execution when placed in the flow editor.
• Implement the ability to pass initial input data to downstream blocks and ensure compatibility with different input types (bool, number, string), with subtypes like JSON if needed.

Measurable 📏: The Start block should trigger any workflow when added to the flow and connected to subsequent blocks. It should successfully pass input data and integrate with other blocks in the system. Unit tests will validate its functionality.

Achievable 🚀: This task is achievable by building upon the base class for blocks, using common methods like execute() and validate(). The Start block will focus on initialization logic and data handling.

Relevant 🎯: The Start block is essential because it initiates all workflows in the system, making it a core part of the user experience.

Time-bound ⏳: This task should be completed within 3 days to ensure it’s ready for integration into the flow editor and testing.

Acceptance Criteria ✅:

• The Start block triggers workflows successfully when placed at the beginning of a flow.
• It passes initial input data (of types bool, number, string, with subtypes like JSON) to downstream blocks.
• Unit tests for the Start block pass, verifying triggering functionality and data passing.
• The Start block integrates seamlessly into the flow editor UI.

[iploooox]

@girl-loves-coding @c0rtexR not sure where this initial input data should come from? Otherwise it looks like this is done just missing tests.

[c0rtexR]

done we will skip tests for now