wagtail.core and wagtail.admin.edit_handlers depreciation #11664
htabar
started this conversation in
Development
Replies: 1 comment
-
Hi, |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey there,
A huge thank you to everyone for your dedication in developing Wagtail.
I've been working on setting up a few Wagtail plugins and projects, but some haven't been updated to accommodate the changes in the old wagtail.core and wagtail.admin.edit_handlers paths! I understand that evolution calls for significant changes, but I wanted to share an idea on how to navigate through these shifts.
I noticed there was a substantial discussion about changing these paths, mentioned here:
https://docs.wagtail.org/en/stable/releases/3.0.html#changes-to-module-paths
By the way, the decision to rename edit_handlers to Panels was a smart move. However, in reality, many plugins and projects on GitHub that previously worked seamlessly with older versions have encountered obstacles. This is especially challenging for newcomers to Wagtail who can't easily perform a simple find and replace!
For these two deprecations, if feasible, I'd even suggest reintroducing the path and the necessary wagtail.core into INSTALLED_APPS. Then, provide the folders and files with a symbolic link to the new path through Python code, if possible.
ModelAdmin Depreciation:
I've checked the discussion on Snippets generalization. Regarding the ModelAdmin deprecation, I strongly recommend reconsidering the strategy used for deprecating wagtail.core and wagtail.admin.edit_handlers, as many plugins are built on top of ModelAdmin.
ModelViewSet, SnippetViewSet, and ModelAdmin essentially serve the same purpose. In my opinion, we could eventually have one unified Wagtalish ModelViewSet, with SnippetViewSet inheriting all the methods from ModelViewSet.
My suggestion for ModelAdmin is to avoid following the same path as wagtail.core and wagtail.admin.edit_handlers. Instead, let's avoid leaving ModelAdmin stranded in code with no utility, just to be used by those stalled apps on GitHub!
Beta Was this translation helpful? Give feedback.
All reactions