sulthan
8e4fa6448e
Closes #136. Spec #136 end to end: `finished` becomes a fact about the Series, written only by the owner, and the reader-facing Lifecycle bucket is gone. ## What landed - **#157** — `series.finished_at bigint NOT NULL DEFAULT 0` plus the migration whose statement order is load-bearing (seed from the buckets, then flip them); both Lane queries lose the `HAVING COUNT(*) FILTER (WHERE b.status <> 'finished')` clause and gate on `finished_at = 0` instead, with the due-query/eligible-count force asymmetry kept deliberate and commented; `StatusFinished`, its API special-case 400, the web tab and the templates' Finished bucket deleted. - **#158** — owner Finish control on the Series detail page: confirm-gated finish, instant un-finish, admin accent (never ember, nothing is destroyed), `Store.SetSeriesFinished`, the two routes behind the owner gate, and the state displayed on the list row without offering the control there. - **#160** — reader side: derived `finished` bool on the flat Bookmark (`s.finished_at > 0`), rendered as a text-only label in both userscripts and on the web card; read-only inbound by omission from `Upsert`'s explicit `series` column list, same mechanism that already protects `cover`. - **#161** — glossary and the stale Reader-count divergence note catch up. - **#159** — `finished` joins the admin filter vocabulary (predicate `finished_at > 0`, label `Finished`, own aggregate count, figure last in the stats block as informational); the four clock-driven hygiene predicates (stale, never-checked, no-cover, no-chapter) exclude finished Series while unpollable, orphan and sighting-raised deliberately do not. ## Verification `go vet ./...` and `go test ./...` green on the merged branch (Docker-backed, throwaway `postgres:17-alpine` per package). Each ticket also passed a two-axis review (spec + standards) on its own branch before merge. Reviewed-on: #163 Co-authored-by: Sulthan Zaki <sultankiki05@gmail.com> Co-committed-by: Sulthan Zaki <sultankiki05@gmail.com>
32 lines
1.6 KiB
HTML
32 lines
1.6 KiB
HTML
{{define "list"}}
|
|
{{if .Items}}
|
|
{{range .Items}}{{template "card" .}}{{end}}
|
|
{{/* The client filter only hides cards, so without this the list area goes
|
|
blank on a query that matches nothing. filter.js fills in the query and
|
|
unhides it; it lives inside #list so a tab swap re-creates it. */}}
|
|
<div class="empty" id="no-match" hidden>
|
|
<strong>No titles match “<span class="no-match-q"></span>”.</strong>
|
|
<button type="button" class="clear-search">Clear search</button>
|
|
</div>
|
|
{{else if eq .Tab "fav"}}
|
|
<div class="empty"><strong>No favourites yet.</strong><p>Star a series to pin it here.</p></div>
|
|
{{else if eq .Tab "new"}}
|
|
<div class="empty"><strong>Nothing new.</strong><p>Every series is caught up to its latest chapter.</p></div>
|
|
{{else if eq .Tab "archived"}}
|
|
<div class="empty"><strong>Nothing archived.</strong><p>Shelve a series to park it here — it keeps getting checked for new chapters.</p></div>
|
|
{{else if .EmptyLibrary}}
|
|
{{/* Nothing in either library, so the links are the only thing this page can
|
|
usefully say. Both scripts: the two libraries are separate installs. */}}
|
|
<div class="empty">
|
|
<strong>Nothing here yet.</strong>
|
|
<p>Install the userscripts, then open a series and read a chapter — bookmarks arrive on their own.</p>
|
|
<p class="setup-links">
|
|
<a class="ghost" href="/install/manga-bookmark.user.js">Install Manga script</a>
|
|
<a class="ghost" href="/install/novel-bookmark.user.js">Install Novels script</a>
|
|
</p>
|
|
</div>
|
|
{{else}}
|
|
<div class="empty"><strong>Nothing here yet.</strong><p>Bookmarks appear once the userscript records a chapter.</p></div>
|
|
{{end}}
|
|
{{end}}
|