Nathaniel Caza


Needs working session/SPIKE/POC to evaluate options

``` ┌──────────────────────────────────────────┐ │ │ │ Create New Service │ │ │ │ ┌────────────────────────────────────┐ │ │ │ Name │ │ │ └────────────────────────────────────┘ │ │ │ │ ┌────────────────────────────────────┐ │ │ │ Description...

Mind map from discussion: 

Yeah, this is a good idea. At the very least, the reason the values are what they are can be documented easily that way. I agree with @ethan-haynes on following...

Maybe part of the validation package? That way the code could read like: ```go validate.ManyUUID("Omit", ids, validate.MaxOmit) ``` Alternatively, we could look into moving from UUID-strings to actual UUIDs (move...

At a high level, here's what this might look like for an SMS provider. The plugin could also be built into GoAlert, but the overall functionality will be the same....

A lot of recent PRs have been made towards this end but were not tagged, for reference: https://github.com/target/goalert/pulls?q=is%3Apr+dest+is%3Aclosed

Would it be acceptable to allow marking a contact method as private? That would give an opt-in way to mark specific numbers (e.g., a roommate or friend's number) but still...

Proposal: - Add a `Private` checkmark to the CM create/edit dialog - Private numbers/cm values hidden in UI (and from API) for non-owning user - Add a `includePrivate` option in...