docs: un-stub Edit Details + Search Author tabs on author detail page (bookshelf-eseay.27) #1374
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "bd-bookshelf-eseay.27"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
docs/content/docs/your-library/authors-series-categories.mdwith accurate end-user descriptionsVerification
templates/pages/author_show.html(Edit Details and Search Author panels) on current main (includes PR #1350) to verify all described fields and controls existstatic/js/controllers/author_search_controller.jsto confirm Search Author queries Audnexus and supports Preview + ApplyTest plan
Closes bead bookshelf-eseay.27 on merge.
Security Review — PR #1374 (bookshelf-eseay.27)
Scope confirmation: Single file changed —
docs/content/docs/your-library/authors-series-categories.md. No Go source, SQL, templates, configuration, or test files are present in this diff. This is a pure documentation update.Findings:
No security findings. Specific checks performed:
SSRF guidance (Set from URL feature): The doc describes the URL-based photo fetch as a plain user action ("paste the URL of a photo on the web") with no suggestion that internal, loopback, or private-network URLs are valid or expected targets. No example URLs, no
localhost/192.168./10.patterns, no implication the feature is unrestricted. The framing is neutral and appropriate for an end-user doc describing a server-mediated fetch that is SSRF-guarded server-side. No unsafe guidance introduced.Permission gating: The Tips section closes with an explicit statement: "The ⋮ button and merge checkboxes are only visible to users who have library management permissions." The Edit Details and Search Author tabs are described as user-facing actions on the author detail page with no claim that they are available to all users unconditionally. The Managing authors / series / categories sections consistently scope admin actions to "Users with library management permissions." No privilege-escalation implication.
Secrets / PII: None present. The ASIN field is documented as a metadata identifier, not a credential. No tokens, API keys, passwords, or personal data referenced.
No code smuggled: Confirmed via
git diff --name-only— exactly one markdown file changed.REVIEW VERDICT: 0 blocker, 0 major, 0 minor
Code / Accuracy Review — PR #1374 (bookshelf-eseay.27)
Reviewed against
origin/maintemplates/pages/author_show.htmlandstatic/js/controllers/author_search_controller.js.Search Author: live vs stub verdict
The earlier review (#1360, comment 16752) saw a
<p class="empty-state">Search Author coming soon.</p>stub. That stub is gone on current main. Thepanel-searchsection on main contains a fulldata-controller="author-search"panel with a real search form, status target, results container, andauthor_search_controller.jsis loaded inpage_scripts. The feature is genuinely live — the doc is correct to describe it as working.Accuracy cross-check
Edit Details tab (doc lines ~31–57)
metadata-fieldinputs presentbtn-lockbeside each input, including photoauthor-edit-photo-formwithtype="file"author-edit-photo-url-formwithtype="url"btn btn-primarysubmit button on the metadata formuploadPhoto/fetchPhotoFromURL)btn-lockwithdata-field="photo"All claims are accurate.
Search Author tab (doc lines ~59–69)
/search-author, 422 triggers "Audnexus is disabled" messagevalue="{{.Author.Name}}"on the input_renderCandidatessetsnameEl.textContentandasinEl.textContent = "ASIN: " + c.asin_renderPreviewExpandrendersimg(photo proxy) +bioEl.textContent = data.bioapply()POSTs ASIN to/apply-authorthenwindow.location.reload()All claims are accurate.
Findings
No inaccuracies, no over-claimed features, no stale stubs left in the doc, no source/route/internal references leaked into the end-user text.
[MINOR] docs/content/docs/your-library/authors-series-categories.md:66 — Preview description omits that it also shows genres
The controller's
_renderPreviewExpandrenders genre chips (data.genres) in addition to the photo and biography, but the doc only says "see the biography and photo that would be imported." The genres are a minor additional detail the user sees but the doc skips. Suggested fix: append ", biography, and other details" instead of just "biography and photo" — or leave as-is if genre display is considered secondary.REVIEW VERDICT: 0 blocker, 0 major, 1 minor
0ad7c08b5bbc88e97092