directus-extension-super-table 0.5.1 → 0.6.2
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.
- package/README.md +6 -0
- package/index.js +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -177,6 +177,12 @@ name clash the most specific (deepest) match wins:
|
|
|
177
177
|
column like `{{treatment.sort}}`
|
|
178
178
|
- `{{<parentField>}}` — a bare token reads a field on the parent row, e.g.
|
|
179
179
|
`{{code}}` shows the order's own code next to each item
|
|
180
|
+
- **Deep paths through the target work too**, including a `translations`
|
|
181
|
+
relation stored inside the target: `{{item:service.translations.label}}`.
|
|
182
|
+
Add a `:lang` suffix to choose the language (`…translations.label:de-DE`);
|
|
183
|
+
without it the current user's language is used. The `:lang` suffix is
|
|
184
|
+
honored on M2A `item:` tokens only; on other relational columns it is not
|
|
185
|
+
interpreted (and an invalid path is dropped rather than sent to the API).
|
|
180
186
|
|
|
181
187
|
Each junction row only resolves the item token whose `<collection>` matches its own
|
|
182
188
|
target, so a template can cover every allowed collection at once:
|