Only pass string addresses to ICS downloads

[adnankussair]

Summary

• Fixes ICS 500s when location is a group/array (Prime location fieldset, empty location: {}, or coords-only) instead of a string.
• Adds icsAddress() so Spatie only receives a non-empty string; keeps the address then string-location fallback.
• ClosesICS download 500s when location is a group/array #183. Reported from passivehouseaccelerator.com#310.
• temp fix until https://github.com/transformstudios/zakat.org/issues/2329 is implemented

Test plan

• ICS download with string address still writes LOCATION:
• ICS download with string location and no address still writes LOCATION:
• ICS download with group/array location and no address returns 200 and omits LOCATION: (single, recurring, multi-day)

---

Note

Low Risk
Localized ICS export fix with type guards and regression tests; no auth, persistence, or API contract changes beyond avoiding errors on array locations.

Overview
Fixes ICS 500 errors when location is a group/array (e.g. Prime location fieldset, empty location: {}, or coords-only) instead of a plain string.

Introduces icsAddress() on the base Event type so Spatie’s iCal builder only receives a non-empty string—still preferring address, then falling back to string location. Single-day, recurring, and multi-day ICS builders all route through this helper instead of passing raw location values.

eventUrl() is aligned to read location via get('location') and skip non-string values before URL checks.

New controller tests cover grouped location without LOCATION: in the file, string location fallback, and the same cases for recurring and multi-day exports.

^{Reviewed by Cursor Bugbot for commit cf61c0c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[adnankussair]

Follow-up: the Rrule → RRule casing cleanup Erin flagged is now in a separate draft PR: #185 (formatting-only, no behavior change).

[edalzell]

@adnankussair thinking through this a bit more, not sure this is the correct fix at all because Events doesn't actually define an address or location field. The location field comes from Prime.

[adnankussair]

@edalzell Agreed that Prime owns the location fieldset and computed address, that is where the group/array shape comes from.

The 500 still happens in Events though. The ICS builder falls back to raw location when address is empty, and Spatie requires a string. Prime already returns a string address when location.details is set; the bug is in Events passing the group array on fallback.

Events is also a standalone package with tests for plain string location on non-Prime installs, so we cannot drop that fallback, we just need to ensure only strings reach Spatie.

Hence no Prime change required to fix the 500.

[edalzell]

Yo cursor, back off, I wanna talk w/ @adnankussair