Right now, when the Serverless Workflows parser reads a workflow.sw.json file, if the attribute "name" is not defined, the parser creates an auto generated "name" with the fixed value "workflow".
This is quite confusing, since users, while querying the DI, etc, will see many workflows with the name "workflow".
Instead, we can generate the "name" with the value of the "id", which is mandatory in the 0.8.0 spec.
In upcoming releases, when we implement Serverless Workflows 0.9.0, and 1.0, we wont have this problem anymore, since, from this version the attribute "id" (mandatory now), will be removed, and we'll only keep the attribute "name", that will be mandatory.
Description
Right now, when the Serverless Workflows parser reads a workflow.sw.json file, if the attribute "name" is not defined, the parser creates an auto generated "name" with the fixed value "workflow". This is quite confusing, since users, while querying the DI, etc, will see many workflows with the name "workflow".
Instead, we can generate the "name" with the value of the "id", which is mandatory in the 0.8.0 spec. In upcoming releases, when we implement Serverless Workflows 0.9.0, and 1.0, we wont have this problem anymore, since, from this version the attribute "id" (mandatory now), will be removed, and we'll only keep the attribute "name", that will be mandatory.
Implementation ideas
No response