1

I am building a CMS that has an abstract definition of an asset.

A page is a collection of assets.

The collection would store details of what is in the collection - but the entities are responsible for their crud process.

I want to be able to manage the collection but have each asset defined in its own bundle - in order to allow 3rd parties to create new asset types.

We are looking at a asset registry / factory pattern.

The process of adding a new asset needs to be dynamic or can be done via a config - but should not require any code changes.

Symfony form types seem to be the closest example to this - any advice / thoughts greatly appreciated.

4

1 に答える 1

0

コンパイラ パスとタグ付きサービスに最適なジョブのようです。

サードパーティは、アセットをサービスとして登録し、特定のタグでタグ付けする必要があります。コンテナーのコンパイル段階で、タグ付けされたすべてのサービスを取得し、それらをサービスに登録します。

関連ドキュメント:

于 2013-03-25T16:21:10.203 に答える