Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explicitly format timestamp in SignatureVerificationError message #1262

Merged
merged 1 commit into from
Aug 22, 2023

Conversation

magni-
Copy link
Contributor

@magni- magni- commented Aug 17, 2023

When interpolating a Time object in a String, Ruby calls to_s under the hood.

For Rails applications defining a default string format, this triggers deprecation warnings as of v7.0.7: rails/rails#48555

This change fixes that by explicitly formatting the timestamp (using the same YYYY-MM-DD HH:mm:ss format currently implicitly used).

@CLAassistant
Copy link

CLAassistant commented Aug 17, 2023

CLA assistant check
All committers have signed the CLA.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link
Contributor

@anniel-stripe anniel-stripe left a comment

Choose a reason for hiding this comment

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

Thanks for opening this PR! This looks great, would you mind fixing the linting error and updating your branch? After that we can hit merge :)

@magni-
Copy link
Contributor Author

magni- commented Aug 22, 2023

@anniel-stripe Thanks for the review, fixed the rubocop offenses and rebased!

When interpolating a Time object in a String, Ruby calls `to_s` under the hood.

For Rails applications defining a `default` string format, this triggers deprecation warnings as of v7.0.7: rails/rails#48555

This change fixes that by explicitly formatting the timestamp (using the same `YYYY-MM-DD HH:mm:ss` format currently implicitly used).
@anniel-stripe
Copy link
Contributor

Thanks for the contribution!

@anniel-stripe anniel-stripe merged commit 79463b2 into stripe:master Aug 22, 2023
11 checks passed
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.

3 participants