Repository navigation
feat: For task #403
Description
Description
Create a dynamic form for the "for" task type that automatically generates form fields based on the for task schema.
Motivation
A dynamic form will ensure that all schema properties are properly exposed to the user
Proposed Implementation
No response
Definition of Done
- Implementation: Fully implemented according to the Open Workflow spec.
- Unit Tests: Comprehensive unit tests are included and passing.
- Integration Tests: Verified within the monorepo and target environments (Web/VS Code).
- Documentation: Updated README.md, ADRs, or official docs.
- Performance: No significant regression in editor responsiveness.
- Accessibility: UI changes comply with accessibility standards.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
handreyrc commentedon Oct 6, 2026
@lornakelly @fantonangeli @kumaradityaraj,
The forTask form is validated and compliant with the schema.
There is no implementation work to be done here because for fields were implemented as sub-set of the call and listen tasks.
Therefore, all custom fields are already functional and available to render a forTask form.
lornakelly commentedon Oct 7, 2026
@handreyrc Maybe some tests could be added? I did the same for do #469
handreyrc commentedon Oct 7, 2026
@lornakelly,
The custom fields used in the forTask form are alredy covered by tests implemented along the call and listen tasks tests.
We already have good test coverage.