Murat Tasan

@sckott, yeah I'm accommodating for now by chunking inputs (e.g. via `readr::read_lines_chunked`), but I thought I'd just raise the issue for awareness :-)

Hi there, just a polite re-surfacing of this issue, which I've run into again. I think breaking up long JSON (character) vectors into chunks works just great and designing a...

An example of an option that'd be nice is `--slurp`, this would make merging arrays a bit easier, like so: ```R x

The easiest way (that I've come up with) to mimic the `--slurp` behavior if you have a vector of JSON array strings, is something like: ```R jq_slurp % jq('flatten') ```...

For cases where none of the resultant columns will be list-cols (e.g. if an API guarantees each sub-list entry is a single value), what about this approach?: ```R got_chars %>%...

I've just noticed that `flatten` does the same thing: ```R > list(Sys.time()) # [[1]] # [1] "2020-11-14 23:34:39 MST" > list(Sys.time()) %>% flatten() # [[1]] # [1] 1605422083 ```

As a follow-on, I've also noticed that `integer(0)` as a key _works_, which seems inconsistent w.r.t. both `character(0)` and `NULL` ... all three of those yield either different results of...

I agree. On Tue, Jul 6, 2021 at 2:28 PM Alberto Negron ***@***.***> wrote: > I agree > > Sent from my iPhone > > > On 6 Jul 2021,...

@wch I'm curious if this approach is frowned-upon (when compared to the 'assign-to-NULL' approach shown above): ```R Klass

I would also love this, as it's the only real blocker to me using emacs-mcx since I work with lots of code written in camelCase :-)