canmove, Confirmed users
1,448
edits
L20n/Features/Conditional blocks: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 27: | Line 27: | ||
This syntax would also allow for [[L20n/Features/Import|import command]] to be encapsulated within such a conditional block. | This syntax would also allow for [[L20n/Features/Import|import command]] to be encapsulated within such a conditional block. | ||
== discussion == | |||
Conditional blocks are at odds with completeness checking. One solution might be to require that the entities in a block are also defined in their default form outside of the block. In this scenario, it might even make sense to use a different keyword, like <code>overload</code> instead of <code>if</code>. | |||
We want to see if there will be a need for grouping variations of entities under a condition. For now, we propose to put this feature on hold. Indexes (like <code>title[@width<600 ? 'long' : 'short']</code>) give us the same functionality and actually have a nice feature to them: the entity is defined in one place only. | |||
== status == | == status == | ||
* stas - | * stas - put on hold | ||
* gandalf - | * gandalf - put on hold | ||
* pike - | * pike - against | ||
* code in [https://github.com/zbraniecki/l20n/tree/statements branch "statements"] | * code in [https://github.com/zbraniecki/l20n/tree/statements branch "statements"] | ||
This is needed for multilocale resources (Gaia) | This is needed for multilocale resources (Gaia) | ||