wtclaude
3d6b2e23a7
Phases 3-4 of docs/website/THEMING_AND_NAV.md. Three presets, the curated font shortlist, and /admin/appearance to drive them. The design put the presets in theme.css as [data-theme] blocks. That does not work: SiteContext writes --accent as an inline style on <html>, which beats any attribute-selector block, so a preset's accent would have been painted over by BRAND_ACCENT_COLOR while getPublic().brand.accent -- the value the Android app themes itself from -- reported the other one. Presets now live in server/src/config/themePresets.js. themeResolve.js layers :root <- preset <- custom per field into a token map, getPublic() returns it as `theme`, and the client writes it onto <html>. One authority for the merge, and brand.accent is by construction the accent the site paints. theme.css's :root is untouched, so an instance with no row gets no theme block and renders as today. Also: presets carry the full 15-token palette (eight would have left Fantasy with blue-grey borders); the option catalog is served from GET /settings/theme/options so the form cannot offer what the server rejects; validation is strict on write and forgiving on read; and the Discord bot now fetches the effective accent instead of its boot-time env copy. Fixes a Phase 0 bug in passing: settings/nav.controller.js imported the logger factory rather than calling it, so a DB fault would have thrown a TypeError inside the catch instead of returning 500. Co-Authored-By: Claude <noreply@anthropic.com>
23 lines
967 B
JavaScript
23 lines
967 B
JavaScript
const settings = require('../../../model/settings/settings.model')
|
|
|
|
// The logger module exports a FACTORY — calling it is what yields {error, warn,
|
|
// info, debug}. Using the factory directly makes `log.error` undefined, which
|
|
// would turn a DB fault into a TypeError thrown inside the catch (no response
|
|
// sent, request left hanging) instead of a 500.
|
|
const log = require('../../../utils/logger')('settings')
|
|
|
|
// The nav overrides for the two authenticated layouts. Values are the raw stored
|
|
// JSON strings (settings.value is TEXT) or null; the caller parses them with the
|
|
// same fail-safe posture as every other JSON setting — malformed reads as
|
|
// absent, and absent means the hardcoded NAV array is used unchanged.
|
|
async function getNav(req, res) {
|
|
try {
|
|
return res.json(await settings.getNav())
|
|
} catch (err) {
|
|
log.error('getNav', err)
|
|
return res.status(500).json({ message: 'Internal Server Error' })
|
|
}
|
|
}
|
|
|
|
module.exports = { getNav }
|