Introduce structured error definitions for GetTreeEntries
GetTreeEntries does not currently return errors when:
- The object ID it gets handled does not point to a treeish.
- The object ID is not a valid reference.
- The requested path does not exist.
This disallows clients to act depending on the exact error conditions.
We thus want to adapt the RPC to start returning structured errors: a new GetTreeEntriesError
message type with a oneof error
should tell the client about the exact failure conditions.
Edited by Patrick Steinhardt