docs: clarify fieldexcludes behavior - #1610
Open
1678092075 wants to merge 1 commit into
Open
Conversation
nodivbyzero
approved these changes
Aug 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes Or Enhances
Fixes #663.
Clarifies the
fieldexcludesdocumentation to match the current implementation:fieldexcludestag instead of the nonexistentexcludesfieldspelling.No runtime behavior or public API changes.
Verification
go test -run '^TestFieldExcludes$' .make testgolangci-lint v2.12.2 rungo doc .AI assistance disclosure
AI assistance was used to search for a non-duplicated contribution candidate, inspect the implementation and existing tests, draft the documentation wording, and run verification commands.
Affected files:
README.mdanddoc.go.Human validation required before submission: review the final two-file diff, confirm the wording matches
fieldExcludesandTestFieldExcludes, and confirm the commands above passed. The contributor remains responsible for the change and should be able to explain it without AI assistance.Make sure that you've checked the boxes below before you submit PR:
TestFieldExcludes).@go-playground/validator-maintainers