decentraland / comms-gatekeeper / 31062185491

86%

main: 86%

Pull #284

github

docs: stop claiming ban status matches token issuance exactly

the note said the endpoint answers 'the same one every token path applies'. that is
not true of the paths that carry a device identifier: they prefer the device on the
request and fall back to the recorded one only when there is none, while this
endpoint receives an address and can only ever use the recorded device. a request
arriving on a device other than the recorded one can disagree with status in either
direction.

narrow both openapi and the architecture note to say what the endpoint actually
does — recorded-device fallback, meant for user-facing ban messaging — and keep
token issuance authoritative for a concrete request.

two test names asserted the same equivalence and are narrowed to the case they
cover, where the device presented is the recorded one.

1145 of 1459 branches covered (78.48%)

Branch coverage included in aggregate %.

3129 of 3527 relevant lines covered (88.72%)

77.55 hits per line