@lotics/cli 0.96.0 → 0.96.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -76,8 +76,15 @@ format handles display.
|
|
|
76
76
|
### Word (`create_word_template`)
|
|
77
77
|
|
|
78
78
|
1. Build a `.docx` with `{{marker}}`s where values go. `lotics upload ./template.docx`.
|
|
79
|
-
2. `create_word_template` with the `template_file_id
|
|
80
|
-
|
|
79
|
+
2. `create_word_template` with the `template_file_id`. `variables` is optional — every
|
|
80
|
+
marker in the document is derived automatically (`{{name}}` → string,
|
|
81
|
+
`{{FOR … IN name}}` → array, `{{IF name}}` → boolean). When you do declare, an unmarked
|
|
82
|
+
declaration comes back in `unmarked_variables` and is skipped, and markers you didn't
|
|
83
|
+
declare are still auto-added (`derived_variables`) — the stored contract always covers
|
|
84
|
+
every marker in the document.
|
|
85
|
+
|
|
86
|
+
At generate time, `data` must provide a key for **every** marker — pass `""` for fields
|
|
87
|
+
that should render blank; a missing key fails with the full list of missing markers.
|
|
81
88
|
|
|
82
89
|
To add markers/loops/conditionals to the uploaded file from the CLI: `word_replace_text`,
|
|
83
90
|
`word_insert_loop`, `word_insert_conditional` (and their `remove_*` counterparts).
|