Commit 68499d8
authored
Fix example test names to comply with Go 1.24 vet checks (#1203)
## What changes are proposed in this pull request?
This PR updates the names of many `Example...` functions in
`*_usage_test.go` files across multiple service packages to comply with
stricter vet rules introduced in Go 1.24.
- **WHAT**: Renamed example functions so that their names match real
exported identifiers.
- **WHY**: In Go 1.24, the `tests` analyzer in `go vet` enforces that
example function names must map to valid exported identifiers. These
stricter checks caused previously valid tests to fail during `go test`,
even though the actual test logic remained unchanged.
## How is this tested?
Validated by running `make test` locally with Go 1.24. All example tests
now pass without build or vet errors.
NO_CHANGELOG=true
Co-authored-by: Omer Lachish <rauchy@users.noreply.github.com>1 parent 68f3330 commit 68499d8
44 files changed
Lines changed: 48 additions & 48 deletions
File tree
- service
- billing
- catalog
- compute
- iam
- jobs
- provisioning
- settings
- sharing
- sql
- workspace
Some content is hidden
Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments