Paul Dix
Paul Dix
I think I prefer alternative 1 as that maps to the API (`/api/v3/query_sql` and `/api/v2/query_influxql`). All the other stuff looks good to me.
Ah right, shortcutting it. I skipped over your "Other Notes". +1 for the `q` and `w` shortcuts 😄
You're right that the expectation is that the `influxdb3 create token` would talk to the server, which would then put the token information into S3. There is a question of...
We already use dotenv and Clap so it loads config flags from command line, environment, file (a `.env` file) in that order.
Oh yeah, we're going to be hitting this all the time. Definitely want to see this! 😁
My guess is that the place where it would be common to mix positional and named arguments would be specifically for optional arguments. As in the required ones would be...
@jlapacik that example was supposed to be a degenerate case where I mixed a positional, required named, and optional named. I assume most people won't be doing that. But mixing...
Wouldn't the type of `f` have to be specified? Like: ``` foo = (f(x=, y=)) => { // stuff here } ```
I was thinking not of specifying the type down to the actual argument types, but only the number of arguments/which named ones exist. Fro example, your definition of `filter` includes...
Also, do we have an example anywhere in the stdlib of a pure Flux function that takes an anonymous function? The only ones I could think of are all defined...