Open denishaskin opened 7 years ago
Hi the problem will be that awesome print will be loading after your initialiser and overriding your defaults with it's own. This may be something we address in the future, but for now, if you put
require 'awesome_print'
just before your defaults, that should address your issue.
Although now that you mention Heroku... I wouldn't recommend using AwesomePrint in your production environment, if that is what you are doing, as it's only really intended for development purposes.
@denishaskin
@gerrywastaken should placing the require call in front of the defaults still get around this?
Is the only way to set defaults for awesome_print through
~/.aprc
?It would be good if it could be done through an initializer, but this doesn't seem to work (this is a Rails app):
Using an external defaults file doesn't play well when using a PaaS platform like Heroku...