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

Explicitly call DeepMerge.deep_merge! #26

Closed
silug opened this issue Nov 25, 2024 · 0 comments · Fixed by #40
Closed

Explicitly call DeepMerge.deep_merge! #26

silug opened this issue Nov 25, 2024 · 0 comments · Fixed by #40

Comments

@silug
Copy link
Contributor

silug commented Nov 25, 2024

In order to prevent conflicts between the activesupport and deep_merge gems, we should explicitly call DeepMerge.deep_merge! instead of the Hash method.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@silug