Stephan Seidt

That could be very useful. The output format for _named positional_ parameters wouldn't have to be all that different from _named destructured_ parameters. Could offer a PR.

Haha, it appears we were thinking of different things. New issue for this use case then? ``` js export const forPythagoreals = ({a, b, c}) => a * a +...

Oh, on a side note: Why is this not using React? If one million people were stuck in one million elevators, maybe it would be good to use React so...

Is this about something other than https://github.com/janmonschke/diffsync#dataadapter? My thoughts: 1. diffsync should always ship with a in-memory implementation by default so people can play with it 2. Could multiple diffsync...

I really don't think it's a problem to have a server peer, and there might be ways to get around that (can operations converge @janmonschke?). The beauty of this is...

Well, looks like #25479 has been merged and there are still problems that could be alleviated by not doing multiple parallel refresh passes. If I call `__refresh` more than once...

I’ve seen similar errors for other fields. Is there any way to include the error message in the response from CraftQL’s side? Might help with debugging in the future.

@hoogw I’ve managed to recompile by changing the Makefile as such: ``` diff CFLAGS = \ -O2 \ -DSQLITE_OMIT_LOAD_EXTENSION \ -DSQLITE_DISABLE_LFS \ - -DSQLITE_ENABLE_FTS3 \ - -DSQLITE_ENABLE_FTS3_PARENTHESIS \ + -DSQLITE_ENABLE_FTS5...

@phiresky Congrats on your very nice blog post. @rhashimoto Off-topic, but I found wa-sqlite and its meta async VFS implementation extremely easy to use. Very well done. It was easy...

A cookbook for this exists now: https://github.com/google-gemini/cookbook/blob/dc168d968b61b0f1603b743bc2deb73723a159f7/quickstarts/Error_handling.ipynb