作者:罗文彬2502852027 | 来源:互联网 | 2023-08-08 08:26
Changes proposed in this pull request:
There should be an ability to manage extensions programatically.
Our goal for Flarum Core is to provide a base for extensions to work with. As such, it makes sense to try to build infrastructure that makes working with extensions easier.
This will also result in a lot of happy users who don't need to manually disable every single extension before upgrading going forward.
Depends on (https://github.com/flarum/core/pull/2068)
Added console commands for:
- Enabling an extension
- Enabling all extensions
- Disabling an extension
- Disabling all extensions
Reviewers should focus on:
- Anything I missed?
Confirmed
- [x] Frontend changes: tested on a local Flarum installation.
- [x] Backend changes: tests are green (run
).
该提问来源于开源项目:flarum/core
Shortened ID is also used to expose all Javascript exports to the global
object, and to store the list of enabled extensions.
I do agree it would make sense to rely on the Composer package name in as many places as possible, in particular for the list of enabled extensions, which then means we can rely on that for all extension management commands.