-
Notifications
You must be signed in to change notification settings - Fork 3
Templating Configuration
- Is in the directory of the executing jar a
cs108pet.configfile with a respectivetemplatingproperty? - Is in the directory of the executing jar a folder
templating? - Is there a
templating.configfile? - Are there any
.templatefiles: - Is in the directory of the executing jar a
templating.configfile? - Uses built in default markdown templates
Essentially, the templating configuration is a JSON-object. See the following example:
{
"extension": "html",
"templates": {
"requirement": "requirement.html",
"milestone": "milestone.html",
"catalogue": "catalogue.txt",
"progress": "progress.asfd",
"group-milestone": "groupMS.md",
"group": "g.template"
}
}
The extension property is mandatory.
The templates is optional, if omitted it is assumed that the template files
are named like the templates properties and have the template extension.
If any of the six properties of templates object is missing, it is assumed
that the default template file (e.g. default template file for requirements:
requirement.template) is present as a sibling of the templating.config file.
One special usage has the symbol #, which stands for that this template is
ignored and thus handled as if there was nothing. Thus in the following
configuration the rendering of milestone would be omitted:
{
"extension":"html",
"templates":{
"milestone":"#"
}
}
Within the cs108pet.config file use the same JSON-object as mentioned above.
The object is named templating:
{
"templating": {
"extension": "tex",
"templates":{
"requirement": "req.tex"
}
}
}