Merge feature/creating-standalone-plugins feature branch#902
Merge feature/creating-standalone-plugins feature branch#902felixarntz merged 178 commits intotrunkfrom
feature/creating-standalone-plugins feature branch#902Conversation
…es-to-standalone-plugins
…ation-ui-from-old-modules-to-standalone-plugins
… plugin managment UI and REST endpoints.
…in applicable load files, enqueue necessary scripts for settings screen.
…dules-to-standalone-plugins
… plugin install actions.
…rocess triggering UI and JS errors.
Update `feature/creating-standalone-plugins` With Latest Trunk
…Press/performance into feature/creating-standalone-plugins
…settings-screen-manage-standalone-plugins
Follow-up: Minor changes for creating standalone plugins
…ointer Implement admin pointer to indicate to the user they need to activate the new standalone plugins
Implement "un-dismiss" migration pointer functionality when the user activates a module
Co-authored-by: Felix Arntz <felixarntz@users.noreply.github.com>
|
The moment has come, it looks like we're ready to merge the feature branch into This PR probably doesn't need a full review as it's all code that has already been reviewed and approved, but another glance over review may still be helpful. Once merged, we'll still have a full week that we can use for testing and fixing any potential bugs we find. Note this PR intentionally has |
|
@felixarntz, while testing the changes, I came across a potential enhancement that requires attention. To address this, I've opened PR #920. |
…ng-page Load migration script in plugin setting page
5 participants
Summary
Fixes #901
This is just a merge PR. All code in this PR has been previously reviewed and approved.
Checklist
[Focus]orInfrastructurelabel.[Type]label.no milestonelabel.