File/package naming convention conforming better to go standards - as ugly as it is

This commit is contained in:
bwilliams committed 2026-10-13 16:31:47 +01:00
1 parent be4770cbab
commit d6688a6754
32 files changed
+36 -36

No files matched your search

+4 -4
View File
@@ -5,10 +5,10 @@ development and testing without hitting the real APIs or their rate limits.
| Package | Mocks | Command |
|---|---|---|
| `findATender` | UK Government Find a Tender service (FTS) OCDS API | `cmd/mock-fts` |
| `findatender` | UK Government Find a Tender service (FTS) OCDS API | `cmd/mock-fts` |
## findATender
## findatender
A mock of the FTS release package endpoint:
```
@@ -81,7 +81,7 @@ Query parameters, as on the real service:
### Generated data
- **Catalog** (`findATender/data/catalog.json`): the buyers, suppliers,
- **Catalog** (`findatender/data/catalog.json`): the buyers, suppliers,
tender subjects, procurement methods and classifications that releases are
drawn from. It's embedded in the binary, so rebuild after changing it.
Subjects refer to classifications by `{scheme}-{id}` keys (e.g.
@@ -111,5 +111,5 @@ Query parameters, as on the real service:
| `ocds/` | Generated OCDS types (`ocds_gen.go`, from `ocdsgen`); don't edit by hand |
| `testdata/` | A small catalog used by the tests |
The mock's `ocds` package is separate from `internal/findATender/ocds`, which
The mock's `ocds` package is separate from `internal/findatender/ocds`, which
the JobSearch client uses.