[16.0][MIG] pim: Migration to 16.0 + remove completeness dependency#184
[16.0][MIG] pim: Migration to 16.0 + remove completeness dependency#184
Conversation
… on models linked to attribute set
* Split computed methods in attribute.set.owner.mixin. * Use assertRaisesRegex in tests to check for exact error message. * Improve readability of event listner skip_if conditions.
add migration script : fields have been removed from v13 -> v14
…r allowing searches
… on models linked to attribute set
attribute_set need 'include_native_attribute' param in context in order to work properly
…tribute_set_completeness' into 16.0-mig-pim
…set_completeness' into 16.0-mig-pim
remove product_attribute_set_completeness dependency on pim
|
Is this replacing completely #165 |
|
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
|
@simahawk The history only reflect what has been done. Feel free to fix that if it really matters, but I guess the number of stuck PR on this project is mainly due to the problem explained in the description. |
History has to be clean. This branch contains merge commits and other things to cleanup. BTW there's a new PR taking care of this #208 . We should probably close this one. |
This PR contains initOS migrations:
and ADD pim_product_attribute_set_completeness
I added a new module
pim_product_attribute_set_completenessto removeproduct_attribute_set_completenessdependency frompim.This dependency was added to display 2 fields in the product list view. This was adding too much complexity to maintain the
pimapp becauseproduct_attribute_set_completenessdepends onattribute_set_completeness, witch depends oncomponent_event(from the 'connector' repository) witch requirescachetoolspython module.pim_product_attribute_set_completeness is now adding product_attribute_set_completeness and add the fields in the pim product list view.