-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
advancedtls: Rename VType #7149
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
security/advancedtls/advancedtls.go
Outdated
// DEPRECATED: Renamed to `VerificationType` | ||
// VType is the verification type on the client side. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The proper way to docstring this is:
// VType is blah blah
//
// Deprecated: use VerificationType instead.
VType VerificationType
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
security/advancedtls/advancedtls.go
Outdated
// the `VerificationType` enum for the different options. | ||
// Default: CertAndHostVerification | ||
VerificationType VerificationType | ||
// DEPRECATED: Renamed to `VerificationType` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
This PR renames
VType
toVerificationType
for clarity.It marks
VType
as deprecated. For now, ifVType
is explicitly set (does not have the default value) then we setVerificationType
toVType
so that user behavior doesn't break.RELEASE NOTES: none