...
| Excerpt Include | |||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
The dumped file will be too big and can cause an overhead for any request, even Cache.
Best practice for Bundles
Best practice for Bundles is described in Symfony documentation under Best Practices for Reusable Bundles, with eZ bundles there is some notable exceptions:
Documentation
- You may write your documentation using markdown (.md) if you prefer, however .rst is recommended if you plan to use writethedocs.org, as heavily used by many open source projects.
Composer Metadata
- For defining
"type", the following are at the moment known valid values:ezpublish-legacy-extension| For standalone 4.x (legacy) extensions, to be used with ezpublish-legacy-installerezpublish-bundle |For eZ Publish Platform 5.x bundles, may optionally be a"legacy bundle".symfony-bundle| Standard symfony bundles as described in Symfony doc.
- For eZ Platform and eZ Studio there is also:
ezplatform-bundle| Symfony bundles that uses eZ Platform features (may also be used by bundles that work across 5.x and 6.xezpublish-kernel)ezstudio-bundle| Symfony bundles that uses eZ Studio features (and optionally also eZ Platform features)