Repository navigation
docs(cities): the form no longer offers Tokyo - #64
Merged
Merged
Conversation
The intake form's city dropdown now lists Japan and New Zealand (2026-11), so the docstring's reason for the fold was stale. The fold itself stays: older rows carry the old cities, and an "Other" answer can still name one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Docstring-only change to
lib/aaif_events/cities.py.The intake form's city dropdown was resynced to the Chapters List on 2026-11-03, so it offers Japan and New Zealand instead of Tokyo and Wellington. The docstring still said the dropdown offered Tokyo. It now says why the fold stays: older rows carry the old cities, and an "Other" answer can still type one.
No behaviour change; library tests pass.
🤖 Generated with Claude Code