Skip to content

utils: mention bytes in force_bytes type error#1173

Open
c-tonneslan wants to merge 1 commit into
jpadilla:masterfrom
c-tonneslan:fix/force-bytes-error-message-mentions-bytes
Open

utils: mention bytes in force_bytes type error#1173
c-tonneslan wants to merge 1 commit into
jpadilla:masterfrom
c-tonneslan:fix/force-bytes-error-message-mentions-bytes

Conversation

@c-tonneslan

Copy link
Copy Markdown

force_bytes accepts str or bytes and returns bytes, but the
fallback TypeError only says "Expected a string value". When the
error fires it reads like the bytes input path is unsupported, even
though it's the second branch in the function itself.

Updated the message to mention both types, and bumped the matching
assertion in test_hmac_should_reject_nonstring_key.

force_bytes accepts str or bytes and returns bytes, so saying
"Expected a string value" when something else lands made the
error read like the bytes case was a bug rather than a supported
input. Wording is the only change.

Signed-off-by: Charlie Tonneslan <cst0520@gmail.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Improves the clarity of jwt.utils.force_bytes’s fallback TypeError by explicitly stating that both str and bytes inputs are supported, and updates the corresponding assertion in the HMAC algorithm tests.

Changes:

  • Update force_bytes to raise TypeError("Expected a string or bytes value") for unsupported input types.
  • Update test_hmac_should_reject_nonstring_key to assert the revised error message.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
jwt/utils.py Adjusts the force_bytes TypeError message to mention both supported input types (str and bytes).
tests/test_algorithms.py Updates the HMAC key rejection test to match the new TypeError message text.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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.

2 participants