要求parent :: __ construct（）的最优雅方式

Question

Say I have the following controller structure:

class Controller {

    public function __construct(){
       $this->accessControl();
    }
}

class Account extends Controller {

   public function __construct(User $user){

      parent::__construct();
      $this->user = $user;
   }
}

How to require other devs to explicitly call parent::__construct() in their child controllers? It contains critical stuff like access control etc

So far I decided to wrap all functions from parent constructor into init() method which sets initialized property to TRUE, then check this property in the router. If it's not TRUE - throw an exceptions.

public $initialized = false;

class Controller {

    public function __construct(){
       $this->init();
    }
}

protected function init(){
   $this->accessControl();
   $this->initialized = true;
}

class Router {
    public function process($path){
       $controller = new User();
       if(!$controller instanceof Controller || !$controller->initialized){
          throw new Exception('Error');
       }
    }
}

Does it smell bad?

Answer 1

The same is needed in Symfony\Console Command, where constructor has to add command name and definition.

They handle it like this in single place where the command is added. So your approach to check controller in Router is the same. I'd got for it, rather then put the responsibility to abstract Controller or some reflection.

---

On the other hand, it looks accessControl() should be checked on security layer level and not in router.

What framework do you use?

Could you decouple it from router by using EventSubscriber and framework event?