mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 20:42:43 +00:00
Marc-André Bombeck
d0b45e36b3
Mood has been a first-class module here for a long time, with entries,
structured tags, rated factors and notes. The bridge to the external moodLog
service had nothing left to add, and its Settings card was withdrawn in
a56e6fe61 on the promise of a dedicated removal. This delivers it.
Removed: the hourly `moodlog-sync` queue, cron and handler binding; the
inbound webhook and its shared-secret handling; the reverse push and its four
call sites; the pull-sync module; the per-user credential routes and the
instance-wide toggle; the entry on the `/api/integrations/status` envelope,
the `IntegrationKey` union, the cadence map and the display-name table; the
boot-time secret rotation pass; 22 message keys per locale.
Migration 0271 drops the five `users` credential columns and
`app_settings.mood_log_global`, clears the ledger row for the provider, and
deletes the retired pg-boss schedule so no cron keeps enqueuing work no
handler drains.
Mood data is untouched. `mood_entries` is not named anywhere in the migration
and cannot be reached from it: the dropped columns carry no index, constraint
or foreign key, and `mood_entries.user_id` references `users(id)`, not any of
them. Rows the bridge imported keep `source = 'MOODLOG'`, and every read path
- list filter, source badge, exports, backups - still resolves that value.
`src/lib/validations/moodlog.ts` held the native mood-entry schemas alongside
the bridge's own; it is now `validations/mood.ts` and carries only the former.
60 lines
1.9 KiB
YAML
60 lines
1.9 KiB
YAML
name: Feature request
|
|
description: Suggest a new feature, integration, or enhancement.
|
|
title: "[Feature] "
|
|
labels: ["enhancement"]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Feature ideas welcome. HealthLog is a personal-health PWA — the bar for inclusion is high (privacy-first, offline-capable, self-hostable). Use this template to propose something concrete; for open-ended discussion, prefer a [Discussion](https://github.com/MBombeck/HealthLog/discussions) thread.
|
|
- type: textarea
|
|
id: problem
|
|
attributes:
|
|
label: Problem
|
|
description: What user problem does this feature solve? "I want to track X but..." is a great opening.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: proposal
|
|
attributes:
|
|
label: Proposed solution
|
|
description: How would the feature work from the user's perspective? Sketches / mocks welcome.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: alternatives
|
|
attributes:
|
|
label: Alternatives considered
|
|
description: What workarounds exist today, and why are they insufficient?
|
|
- type: dropdown
|
|
id: surface
|
|
attributes:
|
|
label: Affected surface
|
|
multiple: true
|
|
options:
|
|
- Web (PWA)
|
|
- iOS app (v1.5+)
|
|
- API
|
|
- Admin
|
|
- Notifications
|
|
- AI Insights
|
|
- Withings integration
|
|
- Self-hosting / Docker
|
|
- Other
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: context
|
|
attributes:
|
|
label: Additional context
|
|
description: Anything else the maintainer should know — links, related issues, prior art.
|
|
- type: checkboxes
|
|
id: terms
|
|
attributes:
|
|
label: Pre-flight checks
|
|
options:
|
|
- label: I confirmed this is not a duplicate of an existing feature request.
|
|
required: true
|
|
- label: I'm proposing a feature, not asking a usage question (those go to Discussions or the docs).
|
|
required: true
|