Potential problems with static properties in Laravel after migrating to Octane | Laravel | Page 1

tender viper Sep 17, 2024, 11:39 PM

#

Hello all,

I have a pre-existing application that I upgraded to Laravel 11. Now, I've been asked to prepare it for Octane (Swoole). From what I can see, only the following class might cause me issues:

class CompanyService
{
    public static $company = null;

    public static function setCompany(Company $company): void
    {
        self::$company = $company;
    }

    public static function getCompany(): ?Company
    {
        return self::$company;
    }
}

Using a middleware, the application determines the active company by calling CompanyService::setCompany(). Then, whenever needed, it retrieves it using CompanyService::getCompany().

If this will cause problems with Octane, how can I adjust it, or what approach should I take?

amber lance Sep 17, 2024, 11:41 PM

#

Use a bind on the service container, potentially using the new attributes (https://laravel.com/docs/11.x/container#defining-custom-attributes) , or reset the static property between requests using an event listener

tender viper Sep 17, 2024, 11:49 PM

#

Thanks. What about https://laravel.com/docs/11.x/context#main-content ? Can it be used for this?

Laravel - The PHP Framework For Web Artisans

Laravel is a PHP web application framework with expressive, elegant syntax. We’ve already laid the foundation — freeing you to create without sweating the small things.

#Potential problems with static properties in Laravel after migrating to Octane