It might be helpfull to calculate the ids for milestone, objectives, deliverables and keyresults.
Just now, the id is calculated during rendering of the template. it would be better to calculate during yaml-processing.
the calculated id should be "_id". given ids from yaml take precendence over calculating.
if "id" is set, we "normalize" id to use in "_id".
If "id" is not set, we calculate "id" and "_id"
Take care that "id" will be displayed and "_id" is used for technical references later, e.g. creating dot-file, make references between deliverbles and keyresults and so on (see #16)...
Benefit is, that the template files will be more readable and the ids are always there.
It might be helpfull to calculate the ids for milestone, objectives, deliverables and keyresults.
Just now, the id is calculated during rendering of the template. it would be better to calculate during yaml-processing.
the calculated id should be "_id". given ids from yaml take precendence over calculating. if "id" is set, we "normalize" id to use in "_id". If "id" is not set, we calculate "id" and "_id"
Take care that "id" will be displayed and "_id" is used for technical references later, e.g. creating dot-file, make references between deliverbles and keyresults and so on (see #16)...
Benefit is, that the template files will be more readable and the ids are always there.