1907/no jira passion deep merge context #11
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
houndci-bot
reviewed
Jul 2, 2019
jebentier
force-pushed
the
1907/no_jira_passion_deep_merge_context
branch
from
eca6ac9 to
9044ee0
Compare
alecjacobs5401
suggested changes
Jul 3, 2019
|
Good call. Thanks for pointing that out. I've gone ahead and added it as a runtime dependency within the gemspec. |
alecjacobs5401
approved these changes
Jul 3, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add Deep merge support
Summary of Changes
This PR is adding the usage of active support's
deep_mergewhen combining context layers together so that sub groupings of context can be updated by various layers.