feat(events): the public calendar, event pages and participation history (Phase 14a)
The anonymous surface an event was always for: GET /public/events, /public/events/:slug and /public/events/series/:slug, plus GET /player/events/history, and the four screens over them. Four org-lead decisions taken up front: split Phase 14 into 14a (website) and 14b (the app); add a `listed` flag rather than letting `state` mean both schedulable and announced; put the `events` capability string in the version block rather than publishing core as a pseudo-module; and drop "venue" from the spec rather than adding a field nothing had ever built. `listed` is announcement, not permission. Publishing is what makes a definition runnable, so without a separate flag a surprise event would have to be advertised in order to be allowed to happen. It is a column, a switch in Phase 13's editor, and three SQL predicates -- never a filter applied after a read, which works exactly as well until the first caller that forgets. The public shapes are a projection, and the projection is the security boundary: nothing is spread, so a column added to event_runs next year does not ride out through it. The spec, health, cleanup, claims, errors and member_key are all absent by construction. The six public event triggers gained `eventUrl` (version 1 -> 2), carrying ?run= because the page lives at the definition's slug while every trigger is about one occurrence. notify.event-started gained the button, at seedVersion 2. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016wDDVXWMDz82WqE1i969r4
This commit is contained in:
68
server/src/router/v1/public/events.controller.js
Normal file
68
server/src/router/v1/public/events.controller.js
Normal file
@@ -0,0 +1,68 @@
|
||||
// Public · Events — the anonymous event surface (EVENTS.md § API surface).
|
||||
//
|
||||
// Phase 14a. Three reads and no writes: the calendar, one event, one arc.
|
||||
//
|
||||
// **Every one of them is a thin pass-through to `eventPublic.model`, and that is
|
||||
// deliberate.** The projection — which fields exist at all on a public entry — is
|
||||
// the security boundary, and it belongs in one file rather than in three
|
||||
// controllers that would each have to remember it. What is left here is the
|
||||
// HTTP: parse the query, map the model's `status` onto a response code, and turn
|
||||
// a thrown read into a 500 rather than a stack trace.
|
||||
//
|
||||
// **A 404 here means "no such public event"** and cannot be told from "no such
|
||||
// slug at all". A draft, an archived definition and an unlisted one answer
|
||||
// identically, which is the whole point: an operator who has not announced
|
||||
// something has not announced its existence either.
|
||||
|
||||
const events = require('../../../model/events/eventPublic.model')
|
||||
const log = require('../../../utils/logger')('public:events')
|
||||
|
||||
const fail = (res, err, what) => {
|
||||
log.error(`${what} failed`, { message: err.message })
|
||||
return res.status(500).json({ message: 'Internal Server Error' })
|
||||
}
|
||||
|
||||
const answer = (res, result) =>
|
||||
result.ok
|
||||
? res.json(result)
|
||||
: res.status(result.status || 400).json({ message: result.errors?.[0] || 'Bad Request', errors: result.errors })
|
||||
|
||||
async function getCalendar(req, res) {
|
||||
try {
|
||||
const seriesId = req.query.seriesId ? Number(req.query.seriesId) : null
|
||||
if (req.query.seriesId && !Number.isInteger(seriesId)) {
|
||||
return res.status(400).json({ message: 'seriesId must be an integer' })
|
||||
}
|
||||
const result = await events.calendar({
|
||||
from: req.query.from || null,
|
||||
to: req.query.to || null,
|
||||
seriesId,
|
||||
})
|
||||
return answer(res, result)
|
||||
} catch (err) {
|
||||
return fail(res, err, 'public calendar')
|
||||
}
|
||||
}
|
||||
|
||||
async function getEvent(req, res) {
|
||||
try {
|
||||
// `run` is optional and un-validated beyond being carried through as a
|
||||
// string: the model matches it against this definition's own runs and
|
||||
// ignores anything else, so a garbage value renders the page rather than an
|
||||
// error. See the model's note on why it is not refused.
|
||||
const result = await events.event(req.params.slug, { runId: req.query.run || null })
|
||||
return answer(res, result)
|
||||
} catch (err) {
|
||||
return fail(res, err, 'public event')
|
||||
}
|
||||
}
|
||||
|
||||
async function getSeries(req, res) {
|
||||
try {
|
||||
return answer(res, await events.series(req.params.slug))
|
||||
} catch (err) {
|
||||
return fail(res, err, 'public series')
|
||||
}
|
||||
}
|
||||
|
||||
module.exports = { getCalendar, getEvent, getSeries }
|
||||
Reference in New Issue
Block a user