Skip to content
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.

Sign up for GitHub

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

Jump to bottom

DeepMerge - avoid conflict with active support #120

Closed
dazza-codes opened this issue Nov 10, 2015 · 1 comment
Closed

DeepMerge - avoid conflict with active support #120

dazza-codes opened this issue Nov 10, 2015 · 1 comment
Assignees
@pkuczynski
Labels
improvement
Milestone
1.2.1

Comments

@dazza-codes
Copy link

See https://github.com/danielsdeleo/deep_merge#using-deep_merge-in-rails

require 'deep_merge/rails_compat'
@pkuczynski pkuczynski added this to the 1.3 milestone May 12, 2016
@pkuczynski pkuczynski self-assigned this May 15, 2016
@pkuczynski pkuczynski mentioned this issue May 26, 2016
Closed
@pkuczynski pkuczynski modified the milestones: 1.2.1, 1.3 May 26, 2016
@pkuczynski
Copy link
Member

This issue is not valid in Config case, as we do not use to_hash method but directly call DeepMerge.merge!

@davidgoldelocks davidgoldelocks mentioned this issue Jan 10, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pkuczynski pkuczynski

Labels
improvement
Milestone
1.2.1
Development

No branches or pull requests
2 participants
@dazza-codes @pkuczynski