The current API leaves it up to clients to reconstruct the full path for entries, either using WorkTree.pathForFileId or by doing its own bookkeeping. This is ok but in an ideal world we'd push that bookkeeping down into Memo instead of rely on clients to do it themselves.
Assuming there is some cost overhead such that Memo wouldn't want to always provide the path, one possibility would be to make it another option clients can pass to WorkTree.entries:
The current API leaves it up to clients to reconstruct the full path for entries, either using
WorkTree.pathForFileIdor by doing its own bookkeeping. This is ok but in an ideal world we'd push that bookkeeping down into Memo instead of rely on clients to do it themselves.Assuming there is some cost overhead such that Memo wouldn't want to always provide the path, one possibility would be to make it another option clients can pass to
WorkTree.entries: