Make 'not found' handling consistent
maritz opened this issue · 0 comments
maritz commented
Currently there are different handlings for different paths of load/find where no result means either an error or an emtpy array. In some cases this can be a bit confusing and a single way to handle 'not found' (and then a NotFoundError instead of default Error) would be better.