Make great documentation goal 1.2, and plan the README's reorganisation and the nested-template gaps #33
@@ -162,9 +162,9 @@ it to a name and read the name
|
|||||||
|
|
||||||
The shipped set under [`data/`](data) — one folder per locale (`en_US`, `sv_SE`),
|
The shipped set under [`data/`](data) — one folder per locale (`en_US`, `sv_SE`),
|
||||||
a `geo` folder of each country's places, and a locale-neutral `misc` folder — is
|
a `geo` folder of each country's places, and a locale-neutral `misc` folder — is
|
||||||
embedded, so the CLI and the library work with no data on disk. A directory is a namespace: each JSON file is a
|
embedded, so the CLI and the library work with no data on disk. A directory is a
|
||||||
category named after the file, each subdirectory a dot-path segment, so
|
namespace: each JSON file is a category named after the file, each subdirectory
|
||||||
`mydata/sv_SE/person.json` is `sv_SE.person` and replaces the shipped one.
|
a dot-path segment, so `mydata/sv_SE/person.json` is `sv_SE.person` and replaces the shipped one.
|
||||||
Sources merge in order; matching folders combine, any other clash is won by the
|
Sources merge in order; matching folders combine, any other clash is won by the
|
||||||
last loaded. Names may not use `.`, `|`, `(`, `{`, `}`, `[`, `]`, `"`, `/` or ` as `,
|
last loaded. Names may not use `.`, `|`, `(`, `{`, `}`, `[`, `]`, `"`, `/` or ` as `,
|
||||||
which binds a [name](#names), nor be `-`, which a struct tag reserves. A dot-prefixed
|
which binds a [name](#names), nor be `-`, which a struct tag reserves. A dot-prefixed
|
||||||
|
|||||||
Reference in New Issue
Block a user