-
Notifications
You must be signed in to change notification settings - Fork 14
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
Using pry 0.13.0 results in the error NoMethodError: undefined method `theme_options' for #<Pry::Config:0x000055dbe462bdd8> #59
Comments
Wow, you still use this gem 😄 |
@kyrylo As long as the default colors of Pry remaing somewhat unpleasant, I will keep using this Gem 😄 |
kyrylo
added a commit
to pry/pry
that referenced
this issue
Apr 12, 2020
Returning `nil` on unknown option was default behaviour for Pry v0.12.x. In e5556a2 I changed that but I am not sure if it was intentional. This breaks plugins such as pry-theme (kyrylo/pry-theme#59). Returning `nil` makes more sense, because we can write code like this: ``` Pry.config.foo ||= 123 ``` ...whereas as of now this is no longer possible and you would need to use `respond_to?` to achieve the same effect.
kyrylo
added a commit
to pry/pry
that referenced
this issue
Apr 12, 2020
Returning `nil` on unknown option was default behaviour for Pry v0.12.x. In e5556a2 I changed that but I am not sure if it was intentional. This breaks plugins such as pry-theme (kyrylo/pry-theme#59). Returning `nil` makes more sense, because we can write code like this: ``` Pry.config.foo ||= 123 ``` ...whereas as of now this is no longer possible and you would need to use `respond_to?` to achieve the same effect.
Fixed by pry/pry#2126 in Pry and released in Pry v0.13.1. |
@kyrylo Thanks! 🎆 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Full error:
This is using the following config:
The text was updated successfully, but these errors were encountered: