Paul Dix
Paul Dix
Also just thinking about readability. Wouldn't function definitions that define the arguments for passed in functions be more readable/understandable? That way the user doesn't have to inspect the function body...
I assume in your example you could also call `from() |> filter(g)`? I like it and I agree that it will be very common to mix positional arguments and named...
Ah, I think I get it. I was reading that positional arguments (without a name) can be optional, but they can't. But does this means position matters even for named...
Heh, wait, so the top one won't throw an error? That is ``` foo = (a, b=1, c="default") => {} foo(23, c: "hello", b: 3) // this is all good...
Awesome, I love it. SHIP IT!
`acknowledge` is for completeness and it's something we may need in the UI at some point. For the responses, we need them on `trigger` if the user doesn't specify a...
What if you want to update multiple columns at the same time or insert a new one and update one? Possible to do? ``` |> map(fn:(r) => {r with {_value:...
I think having all the code for a source in a single file would be great. So having the source be responsible for pushing down logic makes sense. One thing...
I also realized while writing out the PR feedback that there's another setting we'll need for the last values cache, which is an age out. Since it'll keep last values...
I'd like it to be explicit to the user that they're requesting values from the cache. That way they know the semantics behind it (i.e. the cache only has data...