Aaron Boodman

Results 63 issues of Aaron Boodman

See discussion: https://discord.com/channels/830183651022471199/830183651022471202/879401020923478016

user-reported

We currently have a simple `cookie` feature that act like the original HTTP cookies -- the server returns a value in `/replicache-pull` and the client sends that value in next...

Future
Design Needed

This was @arv's idea originally, but I like it... Right now we allow you to create an index anytime you want with `createIndex` and drop them with `dropIndex`. Notably we...

user-reported

See: https://github.com/rocicorp/replicache-react/issues/19 We get asked this enough, we should figure it out. Papercuts and so-on.

Future

See original request here: https://github.com/rocicorp/replicache-todo/issues/2

Future

Right now if most Replicache callback interfaces throw, we catch the error and put it to console. The rationale is that user code is not typically below us in the...

Future
Design Needed

You have a `--cors` option, but it doesn't implement the preflight part of the protocol. This is admittedly a kind of weird thing to ask a static server to do,...

It's pretty common when using `cid.Set` to want them to remain sorted. For example, if you're going to compare two sets, you need them to be sorted. If you're going...

Prior to 0.24.6, this code in my repo works: ``` const supabase = createClient( process.env.NEXT_PUBLIC_SUPABASE_URL!, process.env.NEXT_PUBLIC_SUPABASE_KEY! ); supabase .from(`space:id=eq.${spaceID}`) .on("*", () => { r.pull(); }) .subscribe(); ``` After 0.24.6, the...

bug

Every so often somebody tries to run Chrome on an "insecure domain" and gets an error about crypto being undefined. I don't think we should work around this, but we...