When using custom color defaults by setting AwesomePrint.defaults from anywhere else than ~/.aprc then the custom coloring was gone after the first object had been inspected.
This was due to the permanent removal of the :color key from the given options.
This PR ensures that the given options are not modified.
The builds for all rails gemfiles fail due to an error loading the sqlite3 gem.
Should I address this here or not? I ask, because I think that is nothing related to this PR in general.
When using custom color defaults by setting
AwesomePrint.defaults
from anywhere else than~/.aprc
then the custom coloring was gone after the first object had been inspected. This was due to the permanent removal of the:color
key from the given options. This PR ensures that the given options are not modified.Fixes #209