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
[REQUIRED] Describe the bug
When registering a workflow on the SDK, there is a check that all arguments have metadata Latch parameters. This is super helpful. However, when using Sections and Flow, Params can be missing and then will not be part of the workflow interface.
[REQUIRED] To Reproduce
Test out removing a Param.
For example, consider this flow that accounts for all parameters: flow=[ Section( "Input/Output", Params( "input", "output", ), ), ]
Then, if "input" is removed: flow=[ Section( "Input/Output", Params( "output", ), ), ]
Then the workflow interface will not have a place to specify the input.
[REQUIRED] Expected behavior
It would be awesome if an error were thrown during registration if a Param is missing in the flow Section.
[REQUIRED] Platform Information
macOS Monterey 12.5.1
Chrome: Version 111.0.5563.110
Latch, version 2.15.0
The text was updated successfully, but these errors were encountered:
[REQUIRED] Describe the bug
When registering a workflow on the SDK, there is a check that all arguments have metadata Latch parameters. This is super helpful. However, when using Sections and Flow, Params can be missing and then will not be part of the workflow interface.
[REQUIRED] To Reproduce
Test out removing a Param.
For example, consider this flow that accounts for all parameters:
flow=[ Section( "Input/Output", Params( "input", "output", ), ), ]
Then, if "input" is removed:
flow=[ Section( "Input/Output", Params( "output", ), ), ]
Then the workflow interface will not have a place to specify the input.
[REQUIRED] Expected behavior
It would be awesome if an error were thrown during registration if a Param is missing in the flow Section.
[REQUIRED] Platform Information
The text was updated successfully, but these errors were encountered: