https://github.com/zfcampus/zf-apigility-admin/blob/master/src/ZF/Apigility/Admin/Model/ModuleModel.php#L119
The ability to change which config file a new module is added to, e.g. development.config.php or generated.config.php, would be very helpful.
I don't think anything should ever modify the application.config.php because you'll need to sed out the line if you want to regenerate the module.
Any generated module should be able to be managed by any config file. In our case we generate the API dynamically on each installed machine. Being able to do this by removing the config/generated.config.php file and the /module/Api directory is much easier than removing Api from the module list.
Originally posted by @TomHAnderson at zfcampus/zf-apigility-admin#116
https://github.com/zfcampus/zf-apigility-admin/blob/master/src/ZF/Apigility/Admin/Model/ModuleModel.php#L119
The ability to change which config file a new module is added to, e.g. development.config.php or generated.config.php, would be very helpful.
I don't think anything should ever modify the application.config.php because you'll need to
sedout the line if you want to regenerate the module.Any generated module should be able to be managed by any config file. In our case we generate the API dynamically on each installed machine. Being able to do this by removing the config/generated.config.php file and the /module/Api directory is much easier than removing Api from the module list.
Originally posted by @TomHAnderson at zfcampus/zf-apigility-admin#116