add-ideas/govoplan-calendar
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity

Surface calendar view preferences and complete VEVENT recurrence editing #4

New Issue
Open
opened 2026-07-07 11:53:34 +02:00 by zemion · 1 comment
zemion commented 2026-07-07 11:53:34 +02:00
Owner
Copy Link

Goal

Expose the currently code-level calendar view preferences through the Settings/UI preferences model, and complete user-facing VEVENT/recurrence editing.

Context

The calendar WebUI now has internal defaults/localStorage support for:

  • dimming weekends in week view
  • dimming off-hours, currently defaulting to 06:00-20:00 work time
  • continuous view virtualization/overscan
  • continuous-view alternating month shading

These are intentionally not surfaced in UI yet because core does not have a persisted module-extensible UI preferences panel.

Scope

  • Add a durable settings/preferences path for calendar view defaults and per-user overrides.
  • Surface calendar preferences in the Settings UI once the module settings extension point exists.
  • Add recurrence editing UI for RRULE/RDATE/EXDATE and define how recurrence instances are expanded in views.
  • Expose additional important VEVENT fields in the event editor where appropriate: status, transparency, classification, organizer, attendees, categories, reminders, attachments, related-to, timezone.
  • Preserve unknown iCalendar properties during edits/import/export.

Acceptance Criteria

  • Calendar preferences can be changed without editing localStorage or source constants.
  • Preferences survive reloads and apply consistently across continuous/month/week/workweek/day views.
  • Repeating events can be created, edited, displayed, and moved with clear series-vs-instance behavior.
  • Unsupported/unknown VEVENT data is not silently discarded.
## Goal Expose the currently code-level calendar view preferences through the Settings/UI preferences model, and complete user-facing VEVENT/recurrence editing. ## Context The calendar WebUI now has internal defaults/localStorage support for: - dimming weekends in week view - dimming off-hours, currently defaulting to 06:00-20:00 work time - continuous view virtualization/overscan - continuous-view alternating month shading These are intentionally not surfaced in UI yet because core does not have a persisted module-extensible UI preferences panel. ## Scope - Add a durable settings/preferences path for calendar view defaults and per-user overrides. - Surface calendar preferences in the Settings UI once the module settings extension point exists. - Add recurrence editing UI for RRULE/RDATE/EXDATE and define how recurrence instances are expanded in views. - Expose additional important VEVENT fields in the event editor where appropriate: status, transparency, classification, organizer, attendees, categories, reminders, attachments, related-to, timezone. - Preserve unknown iCalendar properties during edits/import/export. ## Acceptance Criteria - Calendar preferences can be changed without editing localStorage or source constants. - Preferences survive reloads and apply consistently across continuous/month/week/workweek/day views. - Repeating events can be created, edited, displayed, and moved with clear series-vs-instance behavior. - Unsupported/unknown VEVENT data is not silently discarded. <!-- codex-manual-fingerprint:calendar-preferences-vevent-recurrence -->
zemion commented 2026-07-07 14:50:32 +02:00
Author
Owner
Copy Link

Codex State: progress

Summary

  • Replaced the hand-written VEVENT parser/exporter with the icalendar library while preserving unknown properties, parameters, VALARM data, and common unmapped standard properties in event.icalendar.
  • Mapped TZID-aware DTSTART/DTEND/DURATION into UTC storage fields while keeping the source timezone and readable text fields.
  • Added a backend recurrence expansion primitive for RRULE/RDATE/EXDATE; UI recurrence editing and CalDAV/free-busy exposure remain open follow-up work.
  • Changed normal event updates to invalidate stale raw_ics so edited imported events export generated ICS from current fields.

Changed Files

  • pyproject.toml
  • src/govoplan_calendar/backend/ical.py
  • src/govoplan_calendar/backend/service.py
  • tests/test_ical.py

Verification

  • PYTHONPATH=/mnt/DATA/git/govoplan-calendar/src:/mnt/DATA/git/govoplan-tenancy/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-core/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m unittest discover -s /mnt/DATA/git/govoplan-calendar/tests
  • PYTHONPATH=/mnt/DATA/git/govoplan-calendar/src:/mnt/DATA/git/govoplan-tenancy/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-core/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m compileall -q /mnt/DATA/git/govoplan-calendar/src/govoplan_calendar /mnt/DATA/git/govoplan-calendar/tests
  • cd /mnt/DATA/git/govoplan-core && ./.venv/bin/python -m govoplan_core.devserver --smoke --no-reload

Next / Blocked

  • Surface recurrence editing/exception handling in the calendar UI and API.
  • Expose recurrence-expanded listing/free-busy endpoints before CalDAV protocol work.

Suggested status label: status/in-progress

## Codex State: progress ### Summary - Replaced the hand-written VEVENT parser/exporter with the icalendar library while preserving unknown properties, parameters, VALARM data, and common unmapped standard properties in event.icalendar. - Mapped TZID-aware DTSTART/DTEND/DURATION into UTC storage fields while keeping the source timezone and readable text fields. - Added a backend recurrence expansion primitive for RRULE/RDATE/EXDATE; UI recurrence editing and CalDAV/free-busy exposure remain open follow-up work. - Changed normal event updates to invalidate stale raw_ics so edited imported events export generated ICS from current fields. ### Changed Files - `pyproject.toml` - `src/govoplan_calendar/backend/ical.py` - `src/govoplan_calendar/backend/service.py` - `tests/test_ical.py` ### Verification - `PYTHONPATH=/mnt/DATA/git/govoplan-calendar/src:/mnt/DATA/git/govoplan-tenancy/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-core/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m unittest discover -s /mnt/DATA/git/govoplan-calendar/tests` - `PYTHONPATH=/mnt/DATA/git/govoplan-calendar/src:/mnt/DATA/git/govoplan-tenancy/src:/mnt/DATA/git/govoplan-access/src:/mnt/DATA/git/govoplan-core/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m compileall -q /mnt/DATA/git/govoplan-calendar/src/govoplan_calendar /mnt/DATA/git/govoplan-calendar/tests` - `cd /mnt/DATA/git/govoplan-core && ./.venv/bin/python -m govoplan_core.devserver --smoke --no-reload` ### Next / Blocked - Surface recurrence editing/exception handling in the calendar UI and API. - Expose recurrence-expanded listing/free-busy endpoints before CalDAV protocol work. Suggested status label: `status/in-progress`
zemion added the
type
feature
priority
p2
status
triage
module/calendar
codex/ready
 labels 2026-07-07 22:44:24 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
HTTP API contracts, routers, schemas, or API smoke behavior.
area/auth
Authentication, sessions, access bootstrap, or login behavior.
area/db
Database sessions, models, transactions, or persistence primitives.
area/deployment
Deployment, release, operations, or runtime packaging.
area/devex
Local developer workflow, scripts, tests, tooling, or release helpers.
area/docs
Durable documentation and project guidance.
area/governance
Governance policy, audit, privacy, retention, or compliance behavior.
area/marketing
Public website, product messaging, publication copy, or legal page content.
area/migrations
Alembic migrations, schema bootstrap, or persistence evolution.
area/module-system
Module discovery, manifests, capabilities, routing, or optional integrations.
area/rbac
Permissions, roles, delegation, or authorization policy.
area/release
Versioning, release locks, tags, packaging, or dependency pins.
area/security
Security posture, static analysis, supply-chain hardening, or vulnerability remediation.
area/tenancy
Tenant boundaries, provisioning, or tenant-scoped data behavior.
area/webui
Shared WebUI shell, frontend components, routing, or frontend tests.
audit/complexity
Complexity finding from Radon, Xenon, or equivalent maintainability scans.
audit/duplication
Duplicated-code finding from jscpd or equivalent similarity scans.
audit/false-positive
Audit finding reviewed as a narrow false positive or acceptable risk.
audit/needs-design
Audit finding that needs an architectural or product decision before implementation.
audit/quick-fix
Audit finding that appears narrow and directly fixable.
audit/structural
Audit finding that needs design, refactoring, or behavior review.
codex/needs-human
Needs an explicit human decision before Codex should implement.
codex/ready
Suitable for Codex to pick up with the existing issue context.
module/access
GovOPlaN access, identity, authentication, RBAC, and administration behavior.
module/addresses
GovOPlaN Addresses module behavior or integration.
module/admin
GovOPlaN Admin module behavior or integration.
module/appointments
GovOPlaN Appointments module behavior or integration.
module/approvals
GovOPlaN Approvals module behavior or integration.
module/assets
GovOPlaN Assets module behavior or integration.
module/audit
GovOPlaN Audit module behavior or integration.
module/booking
GovOPlaN Booking module behavior or integration.
module/calendar
GovOPlaN Calendar module behavior or integration.
module/campaign
GovOPlaN campaign module behavior or integration.
module/cases
GovOPlaN Cases module behavior or integration.
module/certificates
GovOPlaN Certificates module behavior or integration.
module/committee
GovOPlaN Committee module behavior or integration.
module/connectors
GovOPlaN Connectors module behavior or integration.
module/consultation
GovOPlaN Consultation module behavior or integration.
module/contracts
GovOPlaN Contracts module behavior or integration.
module/core
GovOPlaN core runner, shared primitives, shell, or extension points.
module/dist-lists
GovOPlaN Distribution Lists module behavior or integration.
module/dms
GovOPlaN Dms module behavior or integration.
module/docs
GovOPlaN documentation layer behavior or integration.
module/erp
GovOPlaN Erp module behavior or integration.
module/evaluation
GovOPlaN Evaluation module behavior or integration.
module/facilities
GovOPlaN Facilities module behavior or integration.
module/files
GovOPlaN files module behavior or integration.
module/fit-connect
GovOPlaN Fit Connect module behavior or integration.
module/forms
GovOPlaN Forms module behavior or integration.
module/forms-runtime
GovOPlaN Forms Runtime module behavior or integration.
module/grants
GovOPlaN Grants module behavior or integration.
module/helpdesk
GovOPlaN Helpdesk module behavior or integration.
module/identity
GovOPlaN Identity module behavior or integration.
module/identity-trust
GovOPlaN Identity Trust module behavior or integration.
module/idm
GovOPlaN Idm module behavior or integration.
module/inspections
GovOPlaN Inspections module behavior or integration.
module/issue-reporting
GovOPlaN Issue Reporting module behavior or integration.
module/learning
GovOPlaN Learning module behavior or integration.
module/ledger
GovOPlaN Ledger module behavior or integration.
module/mail
GovOPlaN mail module behavior or integration.
module/notifications
GovOPlaN Notifications module behavior or integration.
module/ops
GovOPlaN Ops module behavior or integration.
module/organizations
GovOPlaN Organizations module behavior or integration.
module/payments
GovOPlaN Payments module behavior or integration.
module/permits
GovOPlaN Permits module behavior or integration.
module/policy
GovOPlaN Policy module behavior or integration.
module/poll
GovOPlaN Poll module behavior or integration.
module/portal
GovOPlaN Portal module behavior or integration.
module/postbox
GovOPlaN Postbox module behavior or integration.
module/procurement
GovOPlaN Procurement module behavior or integration.
module/records
GovOPlaN Records module behavior or integration.
module/reporting
GovOPlaN Reporting module behavior or integration.
module/resources
GovOPlaN Resources module behavior or integration.
module/risk-compliance
GovOPlaN Risk Compliance module behavior or integration.
module/scheduling
GovOPlaN Scheduling module behavior or integration.
module/search
GovOPlaN Search module behavior or integration.
module/tasks
GovOPlaN Tasks module behavior or integration.
module/templates
GovOPlaN Templates module behavior or integration.
module/tenancy
GovOPlaN Tenancy module behavior or integration.
module/transparency
GovOPlaN Transparency module behavior or integration.
module/web
GovOPlaN public website, product page, or publication content.
module/workflow
GovOPlaN Workflow module behavior or integration.
module/xoev
GovOPlaN Xoev module behavior or integration.
module/xrechnung
GovOPlaN Xrechnung module behavior or integration.
module/xta-osci
GovOPlaN Xta Osci module behavior or integration.
priority
p0
Immediate stop-the-line priority.
priority
p1
High priority for the next focused work window.
priority
p2
Normal planned priority.
priority
p3
Low priority or opportunistic cleanup.
source/backlog-import
Imported from markdown backlog, roadmap, plan, or TODO files.
source/module-roadmap
Created from GovOPlaN module and integration roadmap planning.
source/security-audit
Created from a structured security or code-quality audit report.
source/todo-scan
Imported from inline TODO/FIXME/HACK markers by the Gitea TODO importer.
status
blocked
Cannot progress without a decision, dependency, credential, or external change.
status
in-progress
Currently being worked.
status
needs-info
Needs clarifying input before implementation can proceed safely.
status
ready
Ready for implementation.
status
triage
Needs review, ownership, priority, or acceptance criteria.
type
bug
A reproducible defect, regression, or incorrect behavior.
type
debt
Cleanup, refactoring, risk reduction, or deferred engineering work.
type
docs
Documentation, process, or developer workflow work.
type
feature
New user-visible behavior or platform capability.
type
task
Implementation, maintenance, migration, or operational work.
type
user-story
End-to-end user journey or real-world process story used to steer product slices.
No Label
codex/ready
module/calendar
priority
p2
status
triage
type
feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zemion
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-calendar#4
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?