Stephen Haberman

If you `rm -fr foo/` where `foo/` is a tree of `foo/bar/zaz.txt`, the remote side's deleting of `zaz.txt` will tick it's timestamp of `foo/bar` and so make it think that...

Allow the client to sync multiple directories

2

Right now I invoke `mirror client` three times, once per directory I want to sync. The `mirror server` can handle multiple directories, the client should be able to as well.

ts-proto 2.x ideas

9

* ESM output by default * Migrate off long.js * Migrate off protobufjs * Fix `env` to be `node_browser` instead of `both` * Fix `useOptionals` `all` to be `scalar_messages`

Attempting to get a "reproduce bugs that happen in the browser" setup.

Add better return types for toJson methods

2

See #492 but it'd be nice to `.toJson()` to return `JsonOf` or `FooMessageJson` so that API layers that want "basically JSON, but with a few custom mappings" could reuse `.toJson()`...

Upgrade to long 5.0.0 for ESM support

4

In theory some of our import hacks can go away now? Probably needs to be a breaking change for ts-proto as well.

Remove bin files

2

I think with @boukeversteegh 's amazing work around docker-izing the `.bin` generation, I kinda wonder if we could just remove the `*.bin` files all together, and just run `protoc` directly...

I.e. auto-generate: ``` extend type Query { costTypes: [CostTypeDetail!]! } ``` And ``` import { CostTypes } from "src/entities"; import { QueryResolvers } from "src/generated/graphql-types"; export const costTypes: Pick =...

Hooks can see invalid versions of entities

3

I.e. a beforeCreate is passed an `Author` will all of the required fields as-is; but b/c the hook sees the entities before the validation rules have verified the types are...