mirror of
https://github.com/flarum/core.git
synced 2025-10-10 22:44:25 +02:00
Experimenting with some new ways to handle config
For now I’ve chucked it on Flarum\Core as a static method, but ultimately I think we will need a ConfigRepository abstraction (whether it replaces or sits underneath the Flarum\Core static method I’m not sure). Also starting to think about multisite scenarios, I think this is important. The Forum model could actually end up with a database table behind it, and each forum would have its own config settings? Haven’t really thought about it too hard yet…
This commit is contained in:
@@ -18,7 +18,7 @@ class ExtensionsServiceProvider extends ServiceProvider
|
||||
return;
|
||||
}
|
||||
|
||||
$extensions = json_decode(DB::table('config')->where('key', 'extensions_enabled')->pluck('value'), true);
|
||||
$extensions = json_decode(Core::config('extensions_enabled'), true);
|
||||
$providers = [];
|
||||
|
||||
foreach ($extensions as $extension) {
|
||||
|
Reference in New Issue
Block a user