Translatable content type fields
(MGNLUI-4570)
|
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0 |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Oanh Thai Hoang |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | 1h | ||
| Time Spent: | 5d | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Sprint: | Saigon 151 |
| Description |
Composite models:
Given the model below, let's consider two use cases for composite groups:
model:
properties:
- "name"
- "position"
type: Job
subModels:
"Job":
properties:
- "title"
- "organization"
A. Enable `i18n` on the position property
* mika
- name: Mika
* position_fr
- title: Ingénieur Logiciel
- organization: Magnolia International # assuming we don't really translate organization name, but here we could
* position_hr
- title: Softverski Inženjer
- organization: Magnolia International
B. Enable `i18n` on the title property
* mika
- name: Mika
* position
- title_fr: Ingénieur Logiciel
- title_hr: Softverski Inženjer
- organization: Magnolia International # common for all languages here
Multivalue properties:
See also |