Open dantleech opened 11 years ago
that is a weird exception to get for a document not found problem. we might also want to check what is triggering this situation. but either way i agree we should find a way to alert the user what is going wrong. if it includes overhead for sanity checks, we could do those in dev environment only maybe.
ping
@dantleech you where talking about a completely replaced tree bundle for after 1.0 that would be more sane. if we plan that for 1.1, we might just ignore this issue.
ok .. dropping the milestone ..
https://github.com/symfony-cmf/ResourceRestBundle/pull/17 will solve this question for 2.0. After that PR is merged, the result (in case of an undefined root node) will be:
a missing root path will still be a unresolvable situation for the user if the item in that field is required. but at least the DX will be better. would /foo
be the root path? that would mean that i can edit the root path which would be against the idea of limiting what range the user can select from... if the root path is not shown, maybe it should be visible in the error message.
It seems currently that if I specify a non-existant node as the root_node in
doctrine_phpcr_type_tree_model
the backend throws an Exception. I guess it would be good to catch this error and tell the user that the specified root node does not exist.