Add a failing test for M2M models in test_merge_move_detail #202
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
@saxix thanks for building this repo!
I'm trying to debug an issue when I try to merge a couple models with M2M relationships and attempting to create a failing test highlighting the issue.
The main problem is that I'm getting "This field is required" for various M2M fields in the Django admin when I submit the merge.
The first thing I tried to do is simply add a M2M relationship to the
test_merge_move_detailtest that seems to fail per this PR.Should this test be expected to fail in the manner I've adapted it? I would have thought that the M2M relationship would be merged into the preserved model in this test.
Thanks for taking a look!