dantleech
dantleech
``` CREATE /functional/user1 CREATE /functional/user2 CREATE /functional/user2/subuser MOVE /functional/user2/subuser /functional/user1/subuser REMOVE /functional/user2 FLUSH ``` Jackalope-jackrabbit sends the following POST: ``` --0935d494bb0a33542b1ed402934cca2a --0935d494bb0a33542b1ed402934cca2a --0935d494bb0a33542b1ed402934cca2a Content-Disposition: form-data; name=":diff" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding:...
Note that this does not currently address the same problem which this case was designed to reproduce (in [routing auto](https://github.com/symfony-cmf/RoutingAutoBundle/pull/159/files#diff-d35d0adbd9705b4b3930c46cb17ba224R273). In that issue one of the fields caused an undefined...
I will try and have a look at this tomorrow. This is surely [meant to work](https://github.com/doctrine/phpcr-odm/blob/master/lib/Doctrine/ODM/PHPCR/Query/Builder/BuilderConverterPhpcr.php#L242) but couldn't find any existing tests, very odd.
It seems that it would be ideal to add a `$locale` argument to the `loadDocumentsByPhpcrQuery`, but that cascades then to `findMany()` (which can then pass the `locale` hint to the...
Opened issue https://github.com/doctrine/phpcr-odm/issues/623 to discuss how to handle this
just to chip in - i think it should be possible to generate the "name" using an extension. i.e. enabling a method to provide a title which is passed through...
Not sure I understand. a PHPCR `QueryInterface` does not know anything about locales. Why use the PHPCR query object instead of the ODM query builder?
Semantically that would seem strange. "loading" is more appropriate, also it would make the first argument redundant: ``` php $dm->findTranslation('SomeClassNameThatDoesntMatter', $document, 'de'); ``` So I would vote for `loadTranslation` I...
Yeah, and perhaps add an annotation similar to `@Children` which filters the nodes and preserves the array keys. I have basically gotten this working using `@Children` and a pre-persist subscriber:...
> it would mean that custom namespaces for those documents are not supported Not sure I understand the problem? In the case of `nt:file` you would never have a `@Collection`...