docs: api comments say what the endpoints do, not how they came to be (#6277)
Rewrites the internal/api comment blocks to rule 32: task, milestone and rule ids gone, the stories behind them restated as the constraint they left, stale references corrected (the stream secret is wired from config, the timezone handler already refreshes the scheduler, the Android app is the native client, the design docs cited are not in the repo). Also rewraps comment lines over 80 columns left by the earlier batches. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -39,11 +39,11 @@ type yearFilter struct {
|
||||
// the SPA infinite-scrolls against this endpoint via TanStack
|
||||
// createInfiniteQuery.
|
||||
//
|
||||
// Optional filters (#367): `genre` and `year_from`/`year_to`.
|
||||
// Optional filters: `genre` and `year_from`/`year_to`.
|
||||
//
|
||||
// Genre arrives as a QUERY parameter rather than a path segment on purpose.
|
||||
// Raw ID3 genres routinely contain a slash — "Rock/Pop" is a real tag, and
|
||||
// the one the task itself cites — which cannot survive a path segment: Go
|
||||
// Raw ID3 genres routinely contain a slash — "Rock/Pop" is a real tag —
|
||||
// which cannot survive a path segment: Go
|
||||
// normalises %2F and the router would split the value into two segments.
|
||||
func (h *handlers) handleListLibraryAlbums(w http.ResponseWriter, r *http.Request) {
|
||||
limit, offset, err := parsePaging(r.URL.Query())
|
||||
|
||||
Reference in New Issue
Block a user