prometheus/scrape
beorn7 747c5ee2b1 Apply analyzer "modernize" to the whole codebase
See
https://pkg.go.dev/golang.org/x/tools/gopls/internal/analysis/modernize
for details.

This ran into a few issues (arguably bugs in the modernize tool),
which I will fix in the next commit, so that we have transparency what
was done automatically.

Beyond those hiccups, I believe all the changes applied are
legitimate. Even where there might be no tangible direct gain, I would
argue it's still better to use the "modern" way to avoid micro
discussions in tiny style PRs later.

Signed-off-by: beorn7 <beorn@grafana.com>
2025-08-27 14:48:41 +02:00
..
testdata Include test CA text info (#14699) 2024-08-20 19:41:02 +02:00
clientprotobuf.go chore: enable gci linter (#16245) 2025-03-22 15:46:13 +00:00
helpers_test.go chore: enable unused-receiver rule from revive 2025-08-04 09:43:33 +00:00
manager.go Apply analyzer "modernize" to the whole codebase 2025-08-27 14:48:41 +02:00
manager_test.go Apply analyzer "modernize" to the whole codebase 2025-08-27 14:48:41 +02:00
metrics.go Scraping: add metric for symbol table size 2024-07-05 10:16:22 +01:00
scrape.go Apply analyzer "modernize" to the whole codebase 2025-08-27 14:48:41 +02:00
scrape_test.go Apply analyzer "modernize" to the whole codebase 2025-08-27 14:48:41 +02:00
target.go Fix linting issues found by golangci-lint v2.0.2 (#16368) 2025-05-03 19:05:13 +02:00
target_test.go Apply analyzer "modernize" to the whole codebase 2025-08-27 14:48:41 +02:00