Fixes: #42 - Ensure default values are populated in create form for multiobject fields #218
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
arthanson
approved these changes
Sep 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Fixes: #42
Adds logic at the view level to ensure the multiobject form fields are populated with values specified as default (for multiobject fields, these are specified as a list, e.g.
[21, 24]).Note that this functionality is not entirely in line with the behavior for single-object fields, in which a single ID can be specified as a default value and the related object of that ID will automatically be assigned to a new model instance of a custom object created programmatically, i.e.
model(). M2M fields such as this need to be populated after instance creation. This should not be unexpected behavior however, because an instance created withmodel()is not yet persisted and has no ID, so there should be no way to create M2M relations at that stage in its lifecycle.