---
name: Leicester
nomis_id: LCI
address:
- 116 Welford Road
- LE2 7AJ
email: socialvisitsleiceste@hmps.gsi.gov.uk
enabled: true
estate: Leicester
phone: 0116 228 3128
slot_anomalies:
  2014-12-24:
  - 0900-1100
  - 1415-1615
  2014-12-31:
  - 0900-1100
  - 1415-1615
slots:
  mon:
  - 1415-1615
  tue:
  - 1415-1615
  wed:
  - 1600-1800
  thu:
  - 1415-1615
  sat:
  - 1415-1615
  sun:
  - 1415-1615
unbookable:
- 2014-12-25
- 2014-12-26
- 2014-12-31
- 2015-01-01

---
name: Leicester
nomis_id: LCI
address:
- 116 Welford Road
- LE2 7AJ
email: socialvisitsleiceste@hmps.gsi.gov.uk
enabled: true
estate: Leicester
phone: 0116 228 3128
slot_anomalies: {}
slots:
  mon:
  - 1415-1615
  tue:
  - 1415-1615
  wed:
  - 1600-1800
  thu:
  - 1415-1615
  sat:
  - 1415-1615
  sun:
  - 1415-1615
unbookable: []

Fix unbookable and anomalous conflicts on LCI
Fix unbookable and anomalous conflicts on LCI

All of the dates had passed, but I am not confident that the unbookable
and slot_anomalies data structures are not being accessed directly.
The VisitHelper is delegating slot_anomalies to Prison.  It *should* be
using the anomalous_dates method, instead.

I decided against addressing this now as the potential for subtle
breakage feels high and the workaround of including blank data
structures in the yaml solved the problem.

It is worth noting that the specs fail if the unbookable and
slot_anomalies values are left blank.
