Brings #30 (media, blog, projects and photos features; the qbit's own help; a changelog a host can include) from develop into the release branch, so that the next release candidate is published from it. No other change.
Brings #30 (media, blog, projects and photos features; the qbit's own help; a changelog a host can include) from develop into the release branch, so that the next release candidate is published from it. No other change.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Eighteen content tables from the kof22 website's models, as standard QQQ
tables in the qbit's own style: media and media types; blogs, blog types,
authors, blog tags, blog posts with their tags, media and related versions;
project categories, projects and project updates; album folders, photo
albums, photos, photo tags and their links.
- Entities under media/model, blog/model, projects/model and photos/model,
with six value-list enums registered in CmsTables.VALUE_LISTS and produced
as possible-value sources named with the table prefix.
- CmsTableDefinition gains imagePreview, filePreview and help; the table
builder turns them into QQQ file-preview adornments and field help.
- Four more areas (Media, Blogs, Projects, Photos), each with its own home.
- Changelog: 1.0.0-create-<table> for each table, constraints per feature,
two changesets for the links between two features, generic media and blog
type seeds, and a run-once guard against name collisions. Every content
changeset is gated on the features it needs, so a feature can be installed
by a later run and a feature whose needs are missing installs nothing.
- A feature that is off produces nothing; a lookup, a child list or a
foreign key that links two features exists only when both are on.
- Reference DDL regenerated from the changelog on PostgreSQL 17 (the eleven
CORE tables come out unchanged).
Not in this change: file upload, storage and renditions (a media record
points at a file by its address), the publishing processes, the content
stream and the Site API.
Tests: 37 (6 new in CmsContentFeaturesTest), Checkstyle 0, guardrails and
coverage checks pass.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
QQQ offers a fixed list (a possible-value source of an enum) in a form but
accepts any value in a write: through the API a project could be saved with
a status that is not on the list. Found by a live check in a host
application.
- CmsValueListCheck: a pre-insert and pre-update customizer on every table
with a value-list field; a record with another value gets an error and is
not written, and an update is checked only for the fields it names.
- Changelog: check constraints on the same columns (as kof22 has for
media_type and blog_post_version; the project status check is new), and
kof22's checks on media_type.max_file_size_mb and the focal point of a
project's image. They are part of the not yet released
1.0.0-constraints-<feature> changesets.
- Reference DDL regenerated.
Tests: 37, Checkstyle 0, guardrails and coverage checks pass.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
The table label and the home counts read "Medias" and "0 medias". Seen in
the admin of a host application.
Tests: 37, Checkstyle 0, guardrails and coverage checks pass.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
A host should take the CMS whole from this qbit: its tables, its help and
its schema. Two things forced a host to write CMS material of its own; both
are fixed here.
- Help: help/qbit-cms.yaml (643 entries) covers every app, home, table,
section, field, child list and value list. The producer registers it when
the host uses the default names. CmsHelpTest holds it to the core's
coverage gate (HelpBundleAssertions) and to every section.
- Schema: the first guard changeset (1.0.0-guard-existing-tables) no longer
has runAlways. It rewrote its DATABASECHANGELOG row on every migration,
so a second migration was never a no-op and a rollback by count began with
it; a host whose migrations must be repeatable had to copy the tables. It
runs once now, with validCheckSum: ANY so an install that already ran it
migrates on unchanged. This changes a released changeset on purpose;
CmsInstallTest.testRerunIsNoop covers a second run and an install the
earlier version recorded.
- Homes: text sizes in rem (labels 0.875rem instead of 13px), so they follow
the reader's text size.
Tests: 40, Checkstyle 0, guardrails and coverage checks pass.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Brings #30 (media, blog, projects and photos features; the qbit's own help; a changelog a host can include) from develop into the release branch, so that the next release candidate is published from it. No other change.
🤖 Generated with Claude Code