Skip to content

refactor: standardize TLS config fields with tls_ prefix#548

Closed
joaquinhuigomez wants to merge 1 commit into0x676e67:mainfrom
joaquinhuigomez:fix/standardize-tls-field-naming
Closed

refactor: standardize TLS config fields with tls_ prefix#548
joaquinhuigomez wants to merge 1 commit into0x676e67:mainfrom
joaquinhuigomez:fix/standardize-tls-field-naming

Conversation

@joaquinhuigomez
Copy link
Copy Markdown

Rename verify, verify_hostname, identity, and keylog to tls_verify, tls_verify_hostname, tls_identity, and tls_keylog for consistency with the existing tls_info, min_tls_version, max_tls_version, and tls_options fields.

Changes across src/client.rs, python/wreq/wreq.py, tests/tls_test.py, examples/, and docs/.

Closes #545

Rename verify, verify_hostname, identity, and keylog to tls_verify,
tls_verify_hostname, tls_identity, and tls_keylog for consistency
with tls_info, min_tls_version, max_tls_version, and tls_options.

Closes 0x676e67#545
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request renames several TLS-related configuration parameters to include a 'tls_' prefix, specifically updating 'verify', 'verify_hostname', 'identity', and 'keylog' to 'tls_verify', 'tls_verify_hostname', 'tls_identity', and 'tls_keylog' respectively. These changes are applied consistently across the Python type definitions, the Rust backend implementation, documentation, examples, and test suites. I have no feedback to provide.

@0x676e67
Copy link
Copy Markdown
Owner

AI bot?

@0x676e67 0x676e67 closed this Mar 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

standardize configuration field naming

2 participants