check_password sits on the user instance.
Not wired into https://t.co/eMvkbtCJOa yet. Nothing answers on /api/auth/ tonight that didn't answer yesterday.
Lift Day log 21
WIP - password change, backend side.
PasswordChangeSerializer.
Three write_only fields. old_password is checked against the request user before any other rule runs.
PasswordChangeView is the APIView behind IsAuthenticated.
Lift - Day log 20
Six defects the tests had pinned down as xfail are closed. Refresh on a deleted account returns 401 instead of 500, sets refuse negative weight, and a consumed refresh token dies on rotation. 125 tests, no xfail left.
#buildinpublic#django#drf
@WarBornePhoenix hey, when you started DSA, did you just started plain and simple or did you watch youtube tutos / course on how to resolve the problems / roadmap etc ?
Lift - Day log 20
Six defects the tests had pinned down as xfail are closed. Refresh on a deleted account returns 401 instead of 500, sets refuse negative weight, and a consumed refresh token dies on rotation. 125 tests, no xfail left.
#buildinpublic#django#drf
Lift - Daily Log 19
test day
The API now refuses a set written into someone else's session - on create there is no object yet, so object permissions had nothing to compare. One serialiser validator, firing on PATCH too. 124 backend tests, 421 on the front at 84%.
#buildinpublic
Lift - Daily Log 19
test day
The API now refuses a set written into someone else's session - on create there is no object yet, so object permissions had nothing to compare. One serialiser validator, firing on PATCH too. 124 backend tests, 421 on the front at 84%.
#buildinpublic
Lift - Daily Log 18
Design System, Day 3
Screens for the training loop are closed. Start a session, log sets, rest, finalise, find it in the history.
Sets are written optimistically: the row is on screen before the server answers. A dropped connection keeps it, marked NON SYNC
@its_shreeja21 just found out striver sheet in the answers of your tweet and it seems very interesting for the complete beginner. for an intermediate developer i'll say neetcode
Lift - Day Log 16
design system foundation, frontend side:
- flat token file split into two DTCG layers: 27 primitives, 25 semantic roles
- every semantic role traced to a screen in the interface spec — no role without a use
#reactnative#expo#nativewind#buildinpublic
Lift - Daily Log 18
Design System, Day 3
Screens for the training loop are closed. Start a session, log sets, rest, finalise, find it in the history.
Sets are written optimistically: the row is on screen before the server answers. A dropped connection keeps it, marked NON SYNC
Lift Daily Log 17
Design System, Day 2
The palette is fully typed now: 33 primitives, 31 semantic roles, every role traced back to a screen in the spec.
Four monospace families, one per text size — Martian Mono for big figures, Spline Sans for dense set rows.
Volume, Epley 1RM and PR detection sit in one module. same formula on three screens, and warm-up sets are excluded from all of them.
Finish a session and the history groups it under date, with the volume of the working sets only.
Rest timer is a row of cells, one per 15 seconds — the exact step of the +15/−15 buttons.
Nothing animates continuously. A proportional width needs an inline style, and the closed theme has no arbitrary width: the system refuses the sliding bar on its own.