Merge branch 'patch-1' into '662-context-documentation'

Nest multiple component parts by a dot instead of a /

See merge request funkwhale/funkwhale!582
This commit is contained in:
Eliot Berriot 2019-02-07 14:36:51 +01:00
commit 2bc7b00b54
1 changed files with 7 additions and 7 deletions

View File

@ -483,19 +483,19 @@ The detail part, which is optional and refers to the contents of the string itse
Here are a few examples of valid context hierarchies: Here are a few examples of valid context hierarchies:
- ``Sidebar/Player/Button/Title`` - ``Sidebar/Player/Button``
- ``Content/Home/Button/Call to action`` - ``Content/Home/Button/Call to action``
- ``Footer/*/Help text`` - ``Footer/*/Help text``
- ``*/*/*/Verb, Short`` - ``*/*/*/Verb, Short``
- ``Modal/Playlist/Button`` - ``Modal/Playlist/Button``
It's possible to nest multiple component parts to reach a higher level of detail: It's possible to nest multiple component parts to reach a higher level of detail. The component parts are then separated by a dot:
- ``Sidebar/Queue/Tab/Title`` - ``Sidebar/Queue/Tab.Title``
- ``Content/*/Button/Title`` - ``Content/*/Button.Title``
- ``Content/*/Table/Header`` - ``Content/*/Table.Header``
- ``Footer/*/List item/Link`` - ``Footer/*/List item.Link``
- ``Content/*/Form/Help text`` - ``Content/*/Form.Help text``
Collecting translatable strings Collecting translatable strings
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^