Note the motion token drift between CSS and motion.ts

This commit is contained in:
Melvin Strobl
2026-08-15 19:47:09 +02:00
parent bd3b9ac5c5
commit df6b60363e
+4
View File
@@ -8,6 +8,10 @@ Deferring because out of scope is fine, but don't mention deferring than.
## Open ## Open
- BUG/UI: the CSS duration tokens were retuned to 250/500 ms but `lib/motion.ts` still
carries 200/300, so JS animations (panels, dock, tabs) run at a different speed to CSS
transitions. They are meant to mirror each other; pick the intended values and update
`motion.ts` in both repos.
- BUG/API: `pytest tests/` deletes every user on teardown (`tests/conftest.py`), so running - BUG/API: `pytest tests/` deletes every user on teardown (`tests/conftest.py`), so running
it against the development database logs you out of the running app. Point tests at their it against the development database logs you out of the running app. Point tests at their
own database, or reseed with `init_db` afterwards. own database, or reseed with `init_db` afterwards.