-
Notifications
You must be signed in to change notification settings - Fork 548
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
Stripe gem not compatible with awesome print due to metaprogramming method
usage
#524
Comments
Sorry about the trouble and thanks for the report. This is certainly a problem. I'm not quite sure yet what the best way to fix this one is yet. Let me get back to you on it. |
Just a suggestion, @brandur-stripe: For this specific case when a user is normally calling |
@jakeonrails Great point! Thank you for the suggestion; I'll certainly bring it up as a possibility. I suspect that we're going to need a more general approach to this at some point because we're seeing it in a few other places. For example, we smashed Python's |
I'm adding some linters to make sure that we don't introduce anymore of these, and I think we'll probably end up putting in an API version to change the existing instances to something a little better (that's still a little in the air though). |
Fixed released as part of 3.5.3. |
For more info please see the issue here: awesome-print/awesome_print#306 (comment)
For your benefit I re-paste the trace that shows reproduces the error:
Stripe gem version: 2.1.0
Ruby version: 2.2.4
The text was updated successfully, but these errors were encountered: