Closed wfehr closed 11 months ago
any news on this one?
Sorry, this took such a long time. I assume you are tweaking third party plugins this way?
Yes, with the changes added here I can use the project to import/export plugins between different systems. Because of the "mass of different plugins" it is not that easy to implement a general processing of plugins.
For example: django-filer content would currently result in not being able to import/export between systems. But with adding individual code in my project which handles filer-dependencies I can achieve this.
Merging #20 (de3b215) into master (66051dc) will decrease coverage by
0.07%
. The diff coverage is15.38%
.:exclamation: Current head de3b215 differs from pull request most recent head 5a04bf9. Consider uploading reports for the commit 5a04bf9 to get more accurate results
@@ Coverage Diff @@
## master #20 +/- ##
==========================================
- Coverage 31.79% 31.72% -0.07%
==========================================
Files 11 11
Lines 390 394 +4
Branches 57 66 +9
==========================================
+ Hits 124 125 +1
- Misses 266 269 +3
Files Changed | Coverage Δ | |
---|---|---|
djangocms_transfer/importer.py | 20.00% <0.00%> (-1.06%) |
:arrow_down: |
djangocms_transfer/helpers.py | 20.58% <16.66%> (-0.11%) |
:arrow_down: |
djangocms_transfer/datastructures.py | 47.36% <20.00%> (-4.15%) |
:arrow_down: |
Implementing a general handling for all different plugins around is tough to implement, if even possible. The easiest way is to let the user implement custom code for his purposes when exporting and importing. This makes export/import between different systems available.