[REQUEST] allow non-specific date settings for visits

[luclu]

💡 Feature Summary

Allow the visit date to be set to year only or year and month only.

🤔 Problem Statement

Often times I cannot retrospectively reconstruct the exact date of a visit and don't want to put in a false date as a placeholder, like 1.1.2024, but simply 2024 or September of 2023, etc.

🛠️ Proposed Solution

Allow for year-only or year-and-month-only dates in visit dates.

Thank you very much for considering this request!

[madmp87]

Hi @seanmorley15! 👋

Implemented partial date support for visits as requested in #987:

Feature: Allows users to record visits with three precision levels:

1. Full date (YYYY-MM-DD) - exact date known
2. Month+Year (MM/YYYY) - month known, day unknown
3. Year-only (YYYY) - only year known

Backend changes:

• Added date_precision CharField to Visit model with migration
• Updated VisitSerializer with validation
• Included in import/export and calendar views
• Requires start_date on creation (prevents null-date visits)

Frontend changes:

• Dynamic input types: text for MM/YYYY, number for YYYY, native picker for full dates
• Precision selector with visual feedback
• formatPartialDate() and formatPartialDateRange() helpers
• Badges for partial dates in location detail view
• i18n support for all 21 locale files

User experience:

• Seamless switching between precision levels
• Placeholder-to-picker swap pattern
• Clear visual indication of date precision

Status:

• ✅ Fully implemented and tested
• ✅ i18n complete for all languages
• 🔄 Part of upcoming PR bundle

This feature addresses a common user need for recording historical visits
where exact dates aren't known.

Thanks!

[madmp87]

Feature implemented in PR #1009

Summary

Added partial date support for visits, allowing users to record visits with varying levels of date precision instead of requiring a full YYYY-MM-DD date.

Changes

Backend:

• adventures/models.py: Add date_precision CharField to Visit model with choices: full (default), month_year, year_only
• adventures/migrations/0072_visit_date_precision.py: Migration for the new field

Frontend:

• LocationVisits.svelte: Add precision selector UI (three toggle buttons: day/month/year) with dynamic input type switching (date → month → number); visual feedback showing active precision level
• types.ts: Add date_precision to Visit TypeScript interface
• locations/[id]/+page.svelte: Display precision badges in visit timeline and use formatPartialDate() / formatPartialDateRange() helpers for display

i18n:

• Add translation keys for precision labels (date_precision, full_date, month_year, year_only) across all 19 locale files

How It Works

Precision	Input	Stored as	Displayed as
Full date	Date picker	2026-02-15	Feb 15, 2026
Month + Year	Month picker	2026-02-01	02/2026
Year only	Number input	2026-01-01	2026

Testing

• Create visit with each precision level → verify correct input type shows
• Save and reload → precision is preserved
• Location detail view → dates display with correct format and precision badges
• Date range visits → both start and end dates respect precision

[madmp87]

Update: PR #1009 has been rebased onto origin/development to resolve merge conflicts. The branch is now clean and both CI tests (Backend + Frontend) pass.

Implemented in PR #1009 — Partial date support added for visits. Users can now choose between full date (YYYY-MM-DD), month+year (MM/YYYY), or year-only (YYYY) precision when recording visits.