Set genealogy parent correctly to avoid multiple parents #14490
Merged
Conversation
This file contains 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
Set genealogy parent correctly to avoid multiple parents
|
Checked commit Ladas@536483b with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
Fryguy
approved these changes
Mar 24, 2017
|
For backport purposes, #14060 is needed to be backported first (already backported to euwe, but not yet to darga) |
|
@Ladas Is there a BZ for this? Can you please create if it doesn't exist? |
|
@Fryguy did you have a BZ for the "Multiple Parents found" error, or I should create new? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Set genealogy parent correctly to avoid multiple parents.
Only by doing child.parent = parent, we enforce that there can be on 1 parent at the time