• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

MapColonies / shigola / 65bc333c9
57%
master: 44%

Build:
Build:
LAST BUILD BRANCH: chore/drop-vendor
DEFAULT BRANCH: master
Ran 08 Sep 2026 05:21PM UTC
Jobs 1
Files 112
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

08 Sep 2026 05:18PM UTC coverage: 54.242% (+0.06%) from 54.186%
65bc333c9

push

github

web-flow
feat(server): flag a map to serve itself as a whole only (MAPCO-11493) (#20)

* feat(server): flag a map to serve itself as a whole only (MAPCO-11493)

A map publishes a collection for itself and one per layer, so a client can
ask for the whole map or for a single layer of it. Some deployments do not
want the layer tier published at all: the layers are an implementation
detail of the map, and every layer id is a separately cacheable, separately
requestable surface to support.

serve_layer_collections turns that tier off per map. The config key is a
pointer, and so is the atlas field behind it, because the alternative
silently inverts the default: a plain bool makes "unset" indistinguishable
from "explicitly false", which would hide every layer collection in every
config that has never heard of the key -- and, one level down, in every
atlas.Map built as a literal rather than through NewWebMercatorMap, of which
there are two dozen in this tree. nil means the same thing at both hops.

The gate sits in Service.collection and Service.collections, which is all
of it: every route taking a collection id resolves through the former, so
the listing, the collection document, its tilesets and its tiles all stop
answering for a hidden layer together. It is a not-found rather than an
error of its own, because to a client the collection does not exist, and
distinguishing the two would describe the config to anyone who can guess a
layer name.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* docs(ogc): describe serve_layer_collections (MAPCO-11493)

The collections section explains the two-tier model; the flag is the part of
it a map can decline, so it belongs next to the explanation rather than only
in the configuration reference.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* docs(ogc): separate whole-map and layer tiles in the caching section (MAPCO-11493)

The section said tile requests use the same cache keys `shigola... (continued)

12 of 12 new or added lines in 3 files covered. (100.0%)

5287 of 9747 relevant lines covered (54.24%)

130.79 hits per line

Jobs
ID Job ID Ran Files Coverage
1 65bc333c9.1 08 Sep 2026 05:21PM UTC 112
54.24
GitHub Action Run
Source Files on build 65bc333c9
  • Tree
  • List 112
  • Changed 3
  • Source Changed 0
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • 65bc333c on github
  • Prev Build on development (#E49BD3DBC)
  • Next Build on development (#BF16266BF)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc