Skip to content

Add LOCATION to the iCalendar entry model - #166

Open
patrickunterwegs wants to merge 4 commits into
mainfrom
ccr-5c21b43c-3jgxnq
Open

patrickunterwegs wants to merge 4 commits into
mainfrom
ccr-5c21b43c-3jgxnq

Conversation

@patrickunterwegs

Copy link
Copy Markdown
Member

Parse and serialize the RFC 5545 LOCATION property (as written by
Thunderbird and others) into a new IcalEntry.location field, and
persist it in a new IcalEntryDto.location column (migration 13.sqm).

LOCATION used to be an unknown property kept verbatim in
extraProperties. Rows stored that way are lifted into the new field when
read from the database, so an edited location is not serialized twice.

The Claude AI response already returned a location; it is now applied.

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01JkZW9tpCWK1Aib8cuFGrmk

claude and others added 4 commits October 2, 2026 20:21
Parse and serialize the RFC 5545 LOCATION property (as written by
Thunderbird and others) into a new IcalEntry.location field, and
persist it in a new IcalEntryDto.location column (migration 13.sqm).

LOCATION used to be an unknown property kept verbatim in
extraProperties. Rows stored that way are lifted into the new field when
read from the database, so an edited location is not serialized twice.

The Claude AI response already returned a location; it is now applied.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JkZW9tpCWK1Aib8cuFGrmk
Entries stored before LOCATION became a known property keep it in
extraProperties. Only a few testers are affected, so they are told
instead of carrying migration code in the mapper.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JkZW9tpCWK1Aib8cuFGrmk

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants