There is a hook called "not_found" which is not currently taken care of if a non-existent path is requested through iterator interface.
Not sure if it would make sense to wire them together because path actually contains more information than just one missing name -- we could actually be able to detect if user is looking for a missing section or item.
Perhaps a new exception class PathNotFound? And rename NotFound to NameNotFound?
Or just have path and name attributes on NotFound?
Anyway, either the exception has to change or the hook must be wired to stay consistent.
There is a hook called "not_found" which is not currently taken care of if a non-existent path is requested through iterator interface.
Not sure if it would make sense to wire them together because path actually contains more information than just one missing name -- we could actually be able to detect if user is looking for a missing section or item.
Perhaps a new exception class PathNotFound? And rename NotFound to NameNotFound?
Or just have path and name attributes on NotFound?
Anyway, either the exception has to change or the hook must be wired to stay consistent.