Feature/virtual fields & sourcefieldswitcher #31
Merged
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.
Introduces SourceFieldSwitcher, a pseudo-field for allowing a variety of different columns to map to the same destination.
This is super useful for FKs, which you might want to look up by, say,
name
orref
.Tidies up a lot of the form class creation code into a separate
formclassbuilder
file.Drops the need for defining "virtual_fields". This was a lazy way of telling DMI that a field was to be present on the form despite not coming explicitly from the import file. FlatRelatedField was already being handled automatically, however JSONField and anything using CompositeLookupWidgets wasn't. Moving forward, all these fields will just work properly without needing to define stuff in "virtual_fields".