Standardize event IDs #194
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tomasr8
reviewed
Mar 31, 2025
ThiefMaster
reviewed
Apr 7, 2025
alexiri
force-pushed
the
uid
branch
2 times, most recently
from
e9b6aea to
8a976bd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To give calendar software a chance to deduplicate events, all events created by Indico should probably have a common UID. This commit standardizes on the UID used for the current ical exports, defined here. In order to not break backwards compatibility for events created with the previous IDs, we probably need to pick a date after the merge of this change (and deployment to prod, I guess) to switch over. It's ugly, I know, but I can't think of a better solution.