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
{{ message }}
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.
It looks like different steps have different rules for title, for example in direct they start with uppercase, but for split title is the same as the id (except for step-id-kaoto).
Currently the field names are autogenerated by Autoform
The aim is probably to have the title be the source of truth always (is that right?), but a possible workaround to be to set a custom field name only if the title is different from the id. WDYT?
It looks like different steps have different rules for title, for example in direct they start with uppercase, but for split title is the same as the id (except for step-id-kaoto).
Currently the field names are autogenerated by Autoform The aim is probably to have the title be the source of truth always (is that right?), but a possible workaround to be to set a custom field name only if the title is different from the id. WDYT?
This is surprising 👀, were you able to identify in which cases the ID or the Title is used?
In the past, the 'id' and 'title' properties from a step were the same.
With the introduction of KaotoIO/kaoto-backend#650, now
those properties are not the same.
On the UI side, the 'title' property was used to build the parameters of the step, so
in combination with the previous fix, this caused step extensions relying upon
on the previous information are no longer working.
The fix is to use the 'id' property form now on
relates to: #1534
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugSomething isn't workingstep detailRelates to the step detail view
Describe the Bug
It looks like the configuration tab for steps is not using the title for the label of the fields and is instead using the id.
Steps to Reproduce the Bug or Issue
split
to a routeScreenshots or Videos
No response
Platform
The text was updated successfully, but these errors were encountered: