Is your feature request related to a problem? Please describe.
Each node in a graph (a task) should be identifiable. It should be unique within a task scope and can change with each request.
Describe the solution you'd like
The books-listing task configuration below:
Is your feature request related to a problem? Please describe. Each node in a graph (a task) should be identifiable. It should be unique within a task scope and can change with each request.
Describe the solution you'd like The
books-listing
task configuration below:defines two nodes with actions:
book
andte-hbs
. We should not use an action name as a key. The configuration above is transformed to:With this unique node id we should get:
action
)te-hbs
value ).Node identifier should be correctly set in:
io.knotx.fragments.task.factory.node.action.ActionNodeFactory
io.knotx.fragments.task.factory.node.subtasks.SubtasksNodeFactory
Please note that some parts of graph can be configured dynamically (based on fragment or request) so this configuration can not be stored.