We should throw an exception if the basepath does not exist.

[dantleech]

We should throw an exception if the basepath does not exist to avoid the following ambiguous error:

Exception:
[Doctrine\ODM\PHPCR\Id\IdException]
Property "parent" mapped as ParentDocument may not be empty in document of class "Symfony\Cmf\Bundle\RoutingAutoBundle\Model\AutoRoute"

[dantleech]

Releated to: symfony-cmf/symfony-cmf-docs#556

[wouterj]

To be consisted with the other bundles, we should register an initializer instead to create the basepath, don't we?

[lsmith77]

sounds good

[lsmith77]

see #130

[dantleech]

Do we throw an exception if the base path doesn't exist?

[lsmith77]

ah. all i ensure now is that a base path is set and that that path is automatically created. imho it therefore makes no sense to check if the path exists. it must exist or someone is trying pretty hard to break things.

[dantleech]

well, it won't exist if you don't run the initializers, and then people would be like "wtf does that exception message mean¨ :)

[lsmith77]

yes, but 1st of all one should always run the initializers. this is simply something one must do, period. the reason being, if we have to validate the structure on every request, we kill performance. and if you want to do it only once, then you are forgetting that one can simply delete a node later too. unless you have a super smart idea, the best you can do is try and catch the exception of the missing node and then try to determine the cause to give a better exception .. but I am really not sure how feasible this all is. to me it all boils down to: 1) users have to run the initializers 2) users must be aware of the importance of their base paths and their apps should never delete those.

[dantleech]

Well, I am assuming we would only be ensuring that the Parent document is not null when we create the auto route, in which caseiIt won't cost anything. But I will look at it asap.

[lsmith77]

opened #131