...
On line 19, a variable called my_msg is defined with the value of "{{ msg }}". This is Jinja2 syntax that will eventually be replaced with the user specified value for msg (or the default, if they don’t specify anything) during initialization time.
On lines 26 and 29, the message was changed to print the value of my_msg.
...
On line 86 of the snippet above, the value of logLevel was changed from Inherited to {{ log_level | title }}. Once again, this is Jinja2 syntax that will eventually be replaced with the specified value of log_level (or the default, if nothing is specified). Additionally, the built-intitle filter is applied to the value of log_level. This will ensure values like trACe end up as Trace (first letter capitalized and everything else lowercase) as required by template.json.
Step 3 - Packaging the Initial Template
Although the example is a bit contrived, we have managed to create a fully-functional customized template.
To package the template, simply zip up everything into a file called example_template.zip (or whatever you want to call it). Its structure should be as follows (if *.pyc and __pycache__ files are there, it’s fine):
| Code Block |
|---|
Archive: example_template.zip Length Date Time Name --------- ---------- ----- ---- 0 2023-04-04 15:37 __init__.py 306 2023-04-04 15:37 requirements.txt 43 2023-04-05 11:03 setup.cfg 12088 2023-04-05 11:03 setup.py 0 2023-04-05 11:03 src/ 1723 2023-04-05 11:03 src/extension.py 221 2023-04-05 11:03 src/extension.yml 0 2023-04-05 11:03 src/templates/ 3278 2023-04-05 11:09 src/templates/template.json 0 2023-04-04 15:37 src/__init__.py 349 2023-04-05 11:05 template_config.yml --------- ------- 18008 11 files |