docs(server): plain wording in the comments and test titles this change added

Comments and test titles added on this branch cited review labels and
planning documents that do not exist in the repository, and some used
dashes as separators. They now say what the code does and why in plain
sentences, and the Postgres lane's suites share one header format. Test
ids stay as they were.
This commit is contained in:
Maurice
2026-11-18 13:20:09 +01:00
parent e3d195896c
commit 21f4f7d5de
12 changed files with 13 additions and 14 deletions
+2 -3
View File
@@ -5,9 +5,8 @@
* answer a 500 there while SQLite stored it. TREK stores no NUL on either
* engine now (src/db/nul-free.ts): every string a statement carries loses it,
* so the same request answers the same status and leaves the same row on both
* engines (M1 / program rule 22 first made it a 201 on SQLite). The control
* characters 0x01-0x1F, which both engines store, are swept in
* places.test.ts.
* engines. The control characters 0x01-0x1F, which both engines store, are
* swept in places.test.ts.
*/
import { buildApp } from '../../src/bootstrap';
import { Places } from '../../src/db/entities/Places.entity';
+1 -1
View File
@@ -202,7 +202,7 @@ describe('Vacay entries', () => {
});
describe('Vacay carry-over', () => {
it('VACAY-046 — a half day left over carries as a half day into the next year, on every engine', async () => {
it('VACAY-046: a half day left over carries as a half day into the next year, on every engine', async () => {
const { user } = await makeUser(orm);
const cookie = authCookie(user.id);
await request(app).get('/api/addons/vacay/plan').set('Cookie', cookie);