Set not push.#15
Merged
Merged
Conversation
Contributor
Author
|
Looks like the tests are stuck. I'll have to fix before this should be merged. |
AndersDJohnson
force-pushed
the
set-not-push
branch
from
f65d7a2 to
449d9f7
Compare
Contributor
Author
|
Fixed by using |
Owner
|
yes this has bitten me at some point aswell, thx for the PR actually, you might wanna check out #11. I'm using this one in our production app and except for circular dependency checking (which i haven't had the time yet) it does not have most of the issues the current master has. |
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.
For copying, it doesn't make sense to push relations to the new object if existing list may not be empty, e.g. with a default value, or with an existing model using
copyTofrom #14.