Wildcard support

[dantleech]

Closes: #80

Support wildcards via. the CMF resource bundles PhpcrTraversalFinder
class.

Todo:

• Node list
• Node remove
• ... all operatons that accept a path

For node:list:

PHPCRSH > ls tests_general_base/*/jcr:primaryType
/tests_general_base/daniel
+-----------------+------+-----------------+
| jcr:primaryType | NAME | nt:unstructured |
+-----------------+------+-----------------+
/tests_general_base/index.txt
+-----------------+------+---------+
| jcr:primaryType | NAME | nt:file |
+-----------------+------+---------+
/tests_general_base/idExample
+-----------------+------+---------+
| jcr:primaryType | NAME | nt:file |
+-----------------+------+---------+

PHPCRSH > ls tests_general_base/numberPropertyNode/*/special*
/tests_general_base/numberPropertyNode/jcr:content
+--------------+--------+---------------------+
| specialChars | STRING | üöäøéáñâêèàçæëìíîïþ |
+--------------+--------+---------------------+

[dantleech]

Avoid the deprecation errors..

[dbu]

ftr: symfony/symfony#12868

[dantleech]

remove

[dbu]

basically I have created the glob/finder classes in cmf-resource, but it makes no sense to include that package here. It would be better to put it in phpcr.

hmm.. actually I wonder if it should be in symfony-cmf -- we could add globbing support to ORM tree implementations..

if we want to split it out, the correct thing would be to have phpcr/finder or phpcr/phpcr-finder and then have a doctrine/glob-finder or whatever describes that well. or just have it in doctrine/phpcr-odm, using the phpcr-finder if that helps. is there code to be shared for orm glob finding? should it be doctrine/glob-finder and then a phpcr-finder built on top of that?

[dantleech]

Hmm. Well, going down that route there should also be ###/globfinder-common and then implementations in phpcr and doctrine. Argh. I am confused.

[dbu]

doctrine does provide a bunch of generically useful things not tied to object-relational/document-mappers. so doctrine/globfinder could be a thing i guess, if there is enough code to make it worthwile.

[dantleech]

@Ocramius @beberlei do you see any value in adding this library to the Doctrine organization?

It is a library for finding documents based on glob patterns (e.g. $finder->find('/*/foo*')) There are currently implementations for PHPCR + PHPCR-ODM.

[Ocramius]

@dantleech yes, it could be moved to common if there is an interface that could be re-implemented in various other persistence layers.

[dbu]

maybe we should move Symfony\Cmf\Component\Resource\FinderInterface into that library then?
how does this relate to other finder stuff like puli or the symfony finder? not related at all, different concept?

[dantleech]

Yeah the FinderInterface would be a part of this. But if we move it to commons it means that people who only use it for PHPCR (as in this PR) have to pull in the whole of Doctrine commons.

[Ocramius]

I would avoid coupling with the Symfony root namespace (or any other external namespace).

What about defining a package like phpcr (only interfaces) for finder-related tasks?

[dantleech]

Well, the concept could apply equally to any hierarchical data stores, so I wouldn't feel strongly about putting it in a phpcr package.

[Ocramius]

like phpcr: doesn't need to include phpcr in its name

[Ocramius]

Also: we can discuss this on friday/saturday if you are at the mayflower hackaton

[dantleech]

I guess the place that makes most sense would be doctrine/glob-finder although maybe it would just be easier to put it in my own namespace. But yeah, we can all speak about it on Friday :)

[dbu]

there are a couple of separate libraries in doctrine, like annotations. i would prefer to have this in the doctrine organization, as a statement to its role as general glob finder for database-like things. but yeah, lets see on friday :-)

[dantleech]

hmm.. remove this workaround