-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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.
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
Add autocompletion to subflows #2473
Comments
brian-mulier-p
added a commit
that referenced
this issue
Apr 18, 2024
brian-mulier-p
added a commit
that referenced
this issue
Apr 18, 2024
brian-mulier-p
added a commit
that referenced
this issue
Apr 18, 2024
brian-mulier-p
added a commit
that referenced
this issue
Apr 18, 2024
brian-mulier-p
added a commit
that referenced
this issue
Apr 25, 2024
brian-mulier-p
added a commit
that referenced
this issue
Apr 25, 2024
This was referenced May 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, when adding a subflow, you need to know the
namespace
,flowId
andinputs
properties of a subflow.It would be a great improvement to the UX if kestra would provide autocompletion. E.g.:
namespace
, you get autocompletion on theflowId
property based on flows available in that namespace.flowId
, theinputs
map property can give autocompletion of available input propertiesUpdate as of 16.04.2024
Autocompletion
for subflows (autocomplete namespace name first, then autocomplete the flow ID)link
to the subflow flow code in the Editor under the flow ID, allowing users to edit the flow in the same Flow Editor (new Editor tab, not a browser tab → it’s important for Ludo that it's in the same Editor, not a new browser tab). See example to clarify:The text was updated successfully, but these errors were encountered: