docs: correct stale postgresql comment + enrich jwt godoc#7
Merged
Conversation
Late-arriving godoc pass on the bundles: - postgresql: Initialize no longer claims it 'performs migrations if configured' — the bundle does not run migrations (a deployment concern per the package doc); comment now describes validate -> open pool -> apply limits -> ping - jwt: enrich ServiceID/ServiceName (explain context-population mechanism, empty-string-on-no-claims), document TokenValidator.ValidateToken interface method and deepen the TokenValidator type doc Doc comments only; build/vet/lint/tests clean. Co-Authored-By: Claude Fable 5 <[email protected]>
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.
Follow-up doc-comment pass on the bundles (doc comments only, no behavior change).
Initialize's comment claimed it 'performs migrations if configured' — it does not run migrations (a deployment concern per the package doc). Corrected to describe what it actually does: validate → open pool → apply limits → ping.ServiceID/ServiceName(context-population mechanism, empty-string-on-no-claims contract), documented theTokenValidator.ValidateTokeninterface method, and deepened theTokenValidatortype doc.Build, vet, lint (0 issues), and bundle tests all clean.
🤖 Generated with Claude Code