Repository navigation
0012 engine style
Status: accepted · Implementation: done · Date: 2026-11-18
From LibreLifts ADR 0023. Built 2026-11-18: isSetDone, nextSetNumber, planFromRoutine, previousSets, workoutDuration and workoutSummary, with 31 tests. Load in a summary is added weight times reps, per unit; help and holds add nothing to it.
packages/engine holds the rules of the log: how a routine becomes a workout, which sets
count as "last time", what a finished set is, how a workout is summed up
(0006). The app runs these rules and the website may show them. They are
the part of LibreBars that must not be wrong.
Rules written as objects with state are hard to test and hard to trust. date-fns shows another way: a library of small functions that take plain values and return new ones.
- One function per file, named after the function, with its test in a file beside it.
- Plain data in, new values out. Inputs are read-only and are never changed.
- No classes and no hidden state. Calling a function twice with the same arguments gives the same result.
- Nothing impure. A function never reads the clock, storage or the network. When a rule depends on the time, the time is an argument.
-
No dependencies, inside the workspace or outside it. The engine declares the shapes it
takes itself and does not import them from
contracts. - Every function is exported by name from the package's index.
- Loads in different units are never added together. A stored load is kept as entered (0024), so a sum is given per unit.
The same habit is kept outside the engine: a function that reads or writes data takes the database and the current time as arguments.
- Every rule can be tested with a table of inputs and outputs, and read on its own.
- Rules that need many inputs take them all as arguments, which makes some calls long.
- State, such as a person's history, lives in the apps. The engine only computes from what it is given.
- The engine's input shapes and the stored rows are written separately, and the apps map one to the other.
Generated from docs/ on dev. Edit the docs there; changes made on the wiki are overwritten.
- Development
- Workflow
-
Decisions
- 0001 Decisions are recorded
- 0002 Apache License 2.0
- 0003 Changes land on dev by fast-forward; main is the last release
- 0004 Conventional Commits, Keep a Changelog and Semantic Versioning
- 0005 docs/ is for developers and is mirrored to the wiki
- 0006 LibreBars is a free workout log for calisthenics
- 0007 The tracker is an iOS and Android app; its web build stays until the store release
- 0008 LibreBars is an app and a crowd-sourced open database
- 0009 The database is ODbL, media is CC BY-SA, and neither can be closed later
- 0010 A hosted API with a free tier is the paid product
- 0011 The workspace is app, web and api, with engine, ui, data and contracts
- 0012 The engine is small pure functions, in the style of date-fns
- 0013 Web and app share a Tailwind theme, not components
- 0014 Postgres is the source of truth for all data
- 0015 The API is Fastify, and it owns LibreBars accounts
- 0016 Every install is a guest account, made in the background
- 0017 Accounts use Better Auth
- 0018 The on-device database is SQLite with Drizzle, on every platform
- 0019 Sync is our own push and pull
- 0020 The app says it backs up, and backup can be turned off
- 0021 Postgres 18, run with Docker Compose and tested on two databases
- 0022 expo-sqlite is patched so the web build reuses one buffer
- 0023 Seed data is TypeScript modules in packages/data, with permanent ids
- 0024 The first tables
- 0025 One TanStack Start app is the website, on GitHub Pages
- 0026 The catalog reaches the app as a snapshot plus updates, and the website through the API
- 0027 The app's first components are its own