paymentsdb: fix formatting for sql QueryPayments
What changed, and why it matters
This commit only reformats two function definitions in a database helper file, changing how the code is split across lines. There is no change to program logic, SQL queries, or security behavior.
No security action needed; this is a cosmetic style-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff in payments/db/sql_store.go is a pure whitespace/formatting cleanup for the QueryPayments method. It collapses multi-line function signatures for extractCursor and collectFunc onto single lines. No statements, types, query strings, error handling, or control flow are altered.
Changed components
payments/db/sql_store.goInspect captured patch +2 / −6
diff --git a/payments/db/sql_store.go b/payments/db/sql_store.go
index 8030a86..15346ef 100644
--- a/payments/db/sql_store.go
+++ b/payments/db/sql_store.go
@@ -530,9 +530,7 @@ func (s *SQLStore) QueryPayments(ctx context.Context, query Query) (Response,
initialCursor int64
)
- extractCursor := func(
- row sqlc.FilterPaymentsRow) int64 {
-
+ extractCursor := func(row sqlc.FilterPaymentsRow) int64 {
return row.Payment.ID
}
@@ -549,9 +547,7 @@ func (s *SQLStore) QueryPayments(ctx context.Context, query Query) (Response,
}
// collectFunc extracts the payment ID from each payment row.
- collectFunc := func(row sqlc.FilterPaymentsRow) (int64,
- error) {
-
+ collectFunc := func(row sqlc.FilterPaymentsRow) (int64, error) {
return row.Payment.ID, nil
}
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.