bazinga-admin/dashboard-personal
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
60 commits 1 branch 0 tags 810 KiB
  • JavaScript 96.4%
  • CSS 3.4%
  • HTML 0.1%
  • Dockerfile 0.1%
Find a file
Exact
michelle eef38a4442 Read-side migration: prefer task_list.tasks link over legacy project text 
New getProjectName(task) in lib/taskLinks.js is now the single source of
truth for "what project is this task in" - prefers the real link
(task_list.tasks -> directory_projects), falls back to the legacy
project text field when no link exists. Switched every display,
grouping, sort, and membership check across the app onto it: task
rows in Board/Week/Eisenhower/Focus, Area/Project hub task counts,
ProjectDetail's task list, the Home dashboard's goals card and
no-project counter, and task detail/page's project display.

Unlike every other link field on this table, task_list.tasks reads
back FLAT (no junction-wrapping) - confirmed live 16 Aug 2026.

This is read-only - ProjectEditField still writes the text field only,
since writing to the link on an existing task is still blocked (see
email to Noco same day - task_list.tasks is an old field type our API
token can't nestedDataLink/Unlink on). But Noco is already populating
real links from her side while resolving the project-mapping cleanup,
so this isn't just prep - it takes effect immediately for any task she's
already re-linked, even though our own edit UI can't write it yet.
2026-08-16 15:35:54 +01:00
public Board/Week polish: sidebar compact mode, scroll fix, search/filter, week view 2026-08-08 20:59:25 +01:00
src Read-side migration: prefer task_list.tasks link over legacy project text 2026-08-16 15:35:54 +01:00
.dockerignore Initial commit — task manager web app 2026-07-20 22:54:31 +01:00
.env.example Add keyword picker: [keyword] prefix auto-fills area/project/tags 2026-08-14 23:57:42 +01:00
.gitignore Initial commit — task manager web app 2026-07-20 22:54:31 +01:00
.oxlintrc.json Initial commit — task manager web app 2026-07-20 22:54:31 +01:00
docker-compose.yml Initial commit — task manager web app 2026-07-20 22:54:31 +01:00
Dockerfile Initial commit — task manager web app 2026-07-20 22:54:31 +01:00
index.html Board/Week polish: sidebar compact mode, scroll fix, search/filter, week view 2026-08-08 20:59:25 +01:00
nginx.conf Initial commit — task manager web app 2026-07-20 22:54:31 +01:00
package-lock.json Initial commit — task manager web app 2026-07-20 22:54:31 +01:00
package.json Initial commit — task manager web app 2026-07-20 22:54:31 +01:00
README.md Initial commit — task manager web app 2026-07-20 22:54:31 +01:00
session-handoff.md Board/Week polish: sidebar compact mode, scroll fix, search/filter, week view 2026-08-08 20:59:25 +01:00
vite.config.js Initial commit — task manager web app 2026-07-20 22:54:31 +01:00

README.md

React + Vite

This template provides a minimal setup to get React working in Vite with HMR and some Oxlint rules.

Currently, two official plugins are available:

React Compiler

The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.

Expanding the Oxlint configuration

If you are developing a production application, we recommend using TypeScript with type-aware lint rules enabled. Check out the TS template for information on how to integrate TypeScript and Oxlint's TypeScript related rules in your project.