Skip to content

Commit 269f49a

Browse files
manickithiemowmde
authored andcommitted
Use short array syntax in docs for consistency (#693)
1 parent 8b5916f commit 269f49a

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/foreign-entity-ids.wiki

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ When receiving prefixed entities from another repository, prefixes are "chained"
1717

1818
* When reading <code>d:Q5</code> from repository <code>foo</code>, it is turned into <code>foo:d:Q5</code>, meaning ''<code>Q5</code> at the repo that repo <code>foo</code> calls <code>d</code>''
1919
* The local repository may have mappings defined for the prefixes used by other wikis, e.g. <code>foo:d</code> would be known to be the same as the local prefix <code>wd</code> for Wikidata. Mappings are defined as a two-dimensional array, e.g. part of mapping definition for example mentioned here would look like below:
20-
<code> array( ... 'foo' => array( 'd' => 'wd' ), ... )</code>
20+
<code> [ ... 'foo' => [ 'd' => 'wd' ], ... ]</code>
2121

2222
* When deserializing data from another repository, the name of the source repository is always added as a prefix, and then any known mappings are resolved: <code>d:Q5</code> from <code>foo</code> becomes <code>foo:d:Q5</code> and then <code>wd:Q5</code>.
2323
* If no mapping is known, the "chained" version of the ID (<code>foo:d:Q5</code>) is stored locally. If this kind of ID is sent to yet another repo, that may result in longer "chains" of prefixes, like <code>xyz:foo:d:Q5</code>.

0 commit comments

Comments
 (0)