+1 vote

We work with complex entities in a Symfony2 - Propel environment. Most of the time we need to include some scheme-definitions from vendor-packages. A little problem there, adding the external module results in the scheme being editable.

I think it would be a nice feature to make an entire Skipper Module read-only. This feature then should not allow editing a region, nor exporting to the scheme file.

PS. This setting should be save on project level, not in module.xml

asked in Feature Request by (210 points)

1 Answer

0 votes

thanks for suggestion. It should be possible to implement feature which marks whole module as read-only on project level.

Regarding the export, I think there are situation when read-only model should be exported. In your situation I think it's better to remove export settings from module itself, so you never rewrite existing schema files.

answered by Skipper developer (132k points)