Closed CyborgMaster closed 9 years ago
It also seems to happen if I ap
an integer like ap 2
weird.
@CyborgMaster what version of Awesome Print you are using.
1.6.1 (as it shows in the stack trace), which is the latest I believe
@CyborgMaster it is possible to you try awesome_print on a new app, maybe is because some conflict with another gem.
I am using 1.6.1 on a Rails 4.2 project and it is look good to me.
@maurogeorge, sure I'll try that. I'll try and do it tomorrow, because I'm swamped today.
I think it might have something to do with a conflict with either the colored, or the colorize gem, which awesome print seems to be using here.
@CyborgMaster thanks! Waiting for your feedback :heart:
So it looks like this is actually a conflict between the colorize
and colored
gems.
I had the gem capybara-screenshot
in my project which depends on colored
. Updating to the latest version of capybara-screenshot
removed the dependency on colored
and fixed the problem.
So turns out it had nothing to do with aweomse_print
, it just happened to manifest itself whenever I used the ap
command. Sorry for posting the bug report to the wrong project.
Closing.
@CyborgMaster thanks for your feedback, no problem man :smiley:
When I print out ActiveRecord objects in Rails 4.2. I get the following error:
I think this is an awesome print problem. Sorry if it is in another gem.