Commit graph

7 commits

Author SHA1 Message Date
7b04822a9b
Move properties of phones to the phone, not contact_phone
This makes sense because there will naturally be cases where multiple
districts have the same phone number mapped to different contacts.
2026-05-22 20:56:22 +00:00
6175e1a811
Update reporter contact on report update
This is as a complicated one because it involves merging contact
information in tricky cases.

I assume that phone should override email, primarily because setting up
phones is more tightly regulated. This may be a terrible assumption.

Issue: #13
2026-05-21 23:12:36 +00:00
dcce7cda1c
Remove comms.contact_email.id column
The address is the primary key, rather than an ID.
2026-05-21 23:12:36 +00:00
e3cc1e99d1
Update storage of reporter in contact
I failed to retrieve the data correctly before as part of the changeover
to contact records.

Issue: #13
2026-05-21 23:12:36 +00:00
d120ed05f2
Emit communication updated events when reports change
Some checks failed
/ golint (push) Failing after 10s
2026-05-21 04:26:07 +00:00
7237f5f666
Move internal references to new source hosting
Some checks failed
/ golint (push) Failing after 3m50s
2026-05-19 15:33:57 +00:00
f1fe8b4d2b
Add contacts, rework comms schema
This in a pretty huge change. At a high level we're adding the concept
of a 'contact' which is a person or organization that has zero or more
contact methods (email, phone). This ended up cascading a number of
changes, including critically to the publicreprt schema. In the end it
seemed safer to get to the point where I'm confident we aren't using any
of the old fields for storing reporter information (though I haven't
deleted the columns yet) so I removed the code for defining those
columns.

At this point I think it's not possible for me to regenerate the bob
schema due to the interdependencies between my various schemas, so the
migration is well-and-truly happening.
2026-05-15 16:58:28 +00:00