Fix failing validation when saving a new node object with associated parents#21
Closed
MarkMT wants to merge 3 commits intoresgraph:masterfrom
Closed
Fix failing validation when saving a new node object with associated parents#21MarkMT wants to merge 3 commits intoresgraph:masterfrom
MarkMT wants to merge 3 commits intoresgraph:masterfrom
Conversation
…parents Fix flawed test for duplicate record validation
Required for Rails 5.x. See: resgraph#22
Author
|
Closed without comment after 8.5 years? |
|
looks like he renamed his master branch to be the main branch, thus PR gets automatically closed. |
Author
|
If it's just a rename I might re-open against the main branch. However with the repo appearing to have been abandoned all this time, there may not be any point. Leventi's is even older. In any case, I'm happy using my own fork. |
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
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.
This PR resolves issue #20.