-
Notifications
You must be signed in to change notification settings - Fork 24
Add a way to prevent conflicting modules to be activated #644
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## 17.0 #644 +/- ##
==========================================
+ Coverage 73.22% 76.01% +2.79%
==========================================
Files 545 582 +37
Lines 13631 15179 +1548
Branches 1751 1898 +147
==========================================
+ Hits 9981 11539 +1558
+ Misses 3352 3262 -90
- Partials 298 378 +80 ☔ View full report in Codecov by Sentry. |
|




Why is this change needed?
Conflicting modules, such as spp_base (SP-MIS), spp_farmer_registry_base (Farmer Registry) and other associated modules, can be activated by the admin user via the Odoo "Apps" UI. This could lead to errors due to conflicts between the modules. To prevent these issues, "excludes" in the manifest.py of the conflicting modules should be added.
How was the change implemented?
Modify the manifest.py files of the conflicting modules to add the module exclusions.
New unit tests
None
Unit tests executed by the author
None
How to test manually
When installing the following modules, an error will be displayed when its conflicting module is already installed:
SPMIS:
Farmer Registry:
Related links
Add a way to prevent conflicting modules to be activated