search

neos / flow-development-collection

The unified repository containing the Flow core packages, used for Flow development.
https://flow.neos.io/
MIT License
139 stars 188 forks source link

Collection cannot be extended #2876

Open neos-bot opened 10 years ago

neos-bot commented 10 years ago

Jira issue originally created by user @kitsunet:

CollectionInterface is currently pretty useless as it is hard to get Flow to use different implementations than the default one. In ResourceManager::initializeCollections() the collections should be created via ObjectManager->get('CollectionInterface') to allow alternative implementations being used. Alternatively the specific Collection class used could be configurable in Settings similar to Storage and Target.

Jira-URL: https://jira.neos.io/browse/NEOS-788

neos-bot commented 9 years ago

Comment created by @astehlik:

I'm currently looking in the Storage / Collection stuff a bit.

I already uploaded a first proposal to Gerrit: https://review.typo3.org/#/c/37686/

I think the Collection is currently too tightly coupled to the storage. Instead of storing a path pattern it should be possible to store generic options that can be interpreted by the storage. Or even better: get rid of the options in the collection completely and if you want different path patterns configure multiple storages with different paths. I don't see the need for defining the paths in the collection.

Maybe we can chat about this on Slack? I would like to hear some opinions before sticking too much effort in this ;)

kitsunet commented 7 years ago

This belongs to the flow dev collection