Accessing settings and registering them

[danielcharrua]

Hello, I'm struggling to get the settings in some Blade templates using app(GeneralSettings::class)->app_logo_width. This does return an error Class GeneralSettings does not exist at .../vendor/laravel/framework/src/Illuminate/Container/Container.php:877

But if I use app(App\Settings\GeneralSettings::class)->app_logo_width works.

I think that for some reason the GeneralSettings class is not registering into the container and can't be resolved.

Both setting classes are located under app/Settings and namespaced to App\Settings\

My settings.php config file (maybe I'm registering them wrong):

<?php

return [

    /*
     * Each settings class used in your application must be registered, you can
     * put them (manually) here.
     */
    'settings' => [
        App\Settings\GeneralSettings::class,
        App\Settings\NotificationSettings::class
    ],

    /*
     * In these directories settings migrations will be stored and ran when migrating. A settings
     * migration created via the make:settings-migration command will be stored in the first path or
     * a custom defined path when running the command.
     */
    'migrations_paths' => [
        database_path('settings'),
    ],

    /*
     * When no repository was set for a settings class the following repository
     * will be used for loading and saving settings.
     */
    'default_repository' => 'database',

    /*
     * Settings will be stored and loaded from these repositories.
     */
    'repositories' => [
        'database' => [
            'type' => Spatie\LaravelSettings\SettingsRepositories\DatabaseSettingsRepository::class,
            'model' => null,
            'table' => null,
            'connection' => null,
        ],
        'redis' => [
            'type' => Spatie\LaravelSettings\SettingsRepositories\RedisSettingsRepository::class,
            'connection' => null,
            'prefix' => null,
        ],
    ],

    /*
     * The contents of settings classes can be cached through your application,
     * settings will be stored within a provided Laravel store and can have an
     * additional prefix.
     */
    'cache' => [
        'enabled' => env('SETTINGS_CACHE_ENABLED', false),
        'store' => null,
        'prefix' => null,
        'ttl' => null,
    ],

    /*
     * These global casts will be automatically used whenever a property within
     * your settings class isn't a default PHP type.
     */
    'global_casts' => [
        DateTimeInterface::class => Spatie\LaravelSettings\SettingsCasts\DateTimeInterfaceCast::class,
        DateTimeZone::class => Spatie\LaravelSettings\SettingsCasts\DateTimeZoneCast::class,
        Spatie\DataTransferObject\DataTransferObject::class => Spatie\LaravelSettings\SettingsCasts\DtoCast::class,
    ],

    /*
     * The package will look for settings in these paths and automatically
     * register them.
     */
    'auto_discover_settings' => [
        app()->path(),
    ],

    /*
     * Automatically discovered settings classes can be cached so they don't
     * need to be searched each time the application boots up.
     */
    'discovered_settings_cache_path' => storage_path('app/laravel-settings'),
];

Any ideas on what I'm doing wrong? Thank you.

[rubenvanassche]

In blade views you always need to use a fully qualified name, unless you're using Facades like DB. The settings classes aren't facades so a fully qualified name is required.

Personally, I would retrieve the settings within my controller, and then pass them as variables into the views. Then you don't need fully qualified names within your views.