Added tools to track which fields_to_update after mapping. #55
+313
−5
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.
It would be nice if we could find out for mapper what the exact data it is that they are mapping to.
The util
get_mapped_fields
can be used to check which field the mapper will actually update on the to_objproducts_to_db
accepts thefields_to_update
parameter to do partial updates.We can now use a combination of
get_mapped_fields
andProductToModel.get_fields_impacted_by_mapping
to check which fields are actually updated on the product model through a chain of mappings.The output can be directly passed to
products_to_db
as thefields_to_update
parameter