# Always use strings to represent paths over the wire · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/4b1dcf2d55002ded81dfccc4ed93193c51be184c)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 4b1dcf2d55002ded81dfccc4ed93193c51be184c

Requested commit: 4b1dcf2d55002ded81dfccc4ed93193c51be184c

Commit: 4b1dcf2d55002ded81dfccc4ed93193c51be184c

Tree: 7f874a5acf6a2de1e18d53a7c5bc64424b19b429

Author: Antonio Scandurra

Committer: Antonio Scandurra

## Message

```
Always use strings to represent paths over the wire

Previously, the protocol used a mix of strings and bytes without any consistency.

When we go to multiple platforms, we won't be able to mix encodings of paths anyway.
We don't know this is the right approach, but it at least makes things consistent
and easy to read in the database, on the wire, etc. Really, we should be using entry
ids etc to refer to entries on the wire anyway, but there's a chance this is the
wrong decision.

Co-Authored-By: Nathan Sobo <nathan@zed.dev>

```

## Parents

- [974ef967a313868b49f70fe1ea5491adcd9b276d](https://git.cafe/gitcafe/zed/commit/974ef967a313868b49f70fe1ea5491adcd9b276d?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/4b1dcf2d55002ded81dfccc4ed93193c51be184c?format=markdown)