Tom Combet

I'm really sorry for the late help. I'll try to be more active on the project from now on. You're right, we have to call parent `configure()` method in every...

> Hello ! Thanks for your reply :) > > > You're right, we have to call parent configure() method in every command we create. By the way, I prefer...

I don't know what this extension does exactly but if it adds rules about visibility and types, it's already part of PHP-CS-Fixer and PHPStan.

Hi, I can check it next week, not before, sorry.

Very sorry for the late answer, I replied [here](https://github.com/friends-of-presta/fop_console/pull/256#issuecomment-1253502926).

It doesn't really shock me since all the commands concern maintenance mode but I would be okay to split though. So it would be `fop:shop:maintenance-status` and `fop:shop:maintenance-ip`?

I think we could even create the hook by default if it doesn't exist, WDYT?

`fop:hook:list` looks kinda confusing to me. It looks like we want the list of all the hooks. What do you think about `fop:hook:modules`?

We could just remove class_index.php after disabling/enabling override?

I just encountered an issue with this method with my modules: If you define an admin tab linked with a Symfony route and you put the module in quarantine, PrestaShop...