Answer architecture round 8: a shipped package's folder spells its namespace (data/sv_SE, data/geo/SE) under its lowered Go name, as a second bench chose, a mounted root folder reads as its namespace, and item 196 cites goal 9.2
This commit is contained in:
+2
-2
@@ -126,8 +126,8 @@ replacement, and each removed path, column or flag.
|
||||
`sv_SE.sex[f].first-name[Kim]`, and a category with no columns names the record
|
||||
that gives it one.
|
||||
- The shipped data comes in Go packages, one per module, each exporting `FS`:
|
||||
`github.com/larvit/fejkdata/data/enus`, `…/svse`, `…/misc`, `…/geose` and
|
||||
`…/geous`. `data.Modules()`, from `github.com/larvit/fejkdata/data`, lists every one,
|
||||
`github.com/larvit/fejkdata/data/en_US` (package `enus`), `…/sv_SE` (`svse`), `…/misc`,
|
||||
`…/geo/SE` (`geose`) and `…/geo/US` (`geous`). `data.Modules()`, from `github.com/larvit/fejkdata/data`, lists every one,
|
||||
and the CLI carries them all. `New` loads the modules `WithDataFS(modules...)` names and
|
||||
the folders `WithDataPath` names, and fails, naming `WithDataFS`, where no such option
|
||||
is given. A manifest's `namespace` mounts its source under a dot path.
|
||||
|
||||
Reference in New Issue
Block a user