feat(calendar): full-day scheduling grid that scrolls in its box (MAPPS-387) #448
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/MAPPS-387-full-day-scheduling-grid"
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?
MAPPS-387: scheduling grid spans midnight to midnight and scrolls in its box
Replaces the fixed 7 AM to 7 PM scheduling window with a full 24-hour axis across the week grid, day grid, and dispatch timeline. Every hour is now schedulable; hours outside typical working hours are visually de-emphasized rather than treated as unavailable. Axis labels stay 12-hour AM/PM (no 24-hour "18" for 6 PM).
What changed
GRID_START_HOUR/GRID_END_HOURare now 0/24).max-h-[70vh]) instead of the page; the week view's day-of-week header sticks to the top. On mount each grid/timeline defaults its scroll to the working-hours window (7 AM to 7 PM).bg-surface-2), not struck through, and remain fully selectable (the create-on-click path still fires on them).span_geometryused by both the vertical blocks and the horizontal dispatch bars. An appointment crossing local midnight fills to end-of-grid instead of inverting.WORK_START_HOUR/WORK_END_HOUR) pending a per-user / per-workspace setting, which should be filed separately.Tests
grid_geometry_tests: full-range rendering, in-hours and out-of-hours offsets, no-clamp behavior, grid-edge clamping, min-size floor, and the working-hours window / shading helpers.cargo test --libgreen (230 passed).cargo fmt --all --check,cargo clippy --all-targets -- -D warnings, andcargo check --target wasm32-unknown-unknownall pass on the 1.94.1 toolchain (matches CI).Commits
Split into three logical steps: (1) full-day geometry + working-hours constants + tests, (2) day/week grid scroll-in-box + off-hours shading, (3) dispatch timeline full-day + shading.
Acceptance criteria