Tarek Rached

FWIW, I was able to do this by pulling some attrs out of the pivot state in the `PivotTableUI` `onChange` handler, and then stuffing the attrs in a JSON encoded...

Pedantically speaking, wouldn't this be `undefined` for the missing values, rather than `null`?

Happy to contribute any debug info from my [LG LW1517IVSM](https://www.lg.com/us/air-conditioners/lg-lw1517ivsm) - let me know what would be useful!

looks like it's [this extension](https://github.com/jasonlong/isometric-contributions)

Right on. I'm not sure that I'd remove the warning message, though. The warning makes sense given the current behavior: `useQueryParams` adds all queryparams to the `DecodedValueMap`, regardless of whether...

In terms of prioritization, that totally makes sense - no rush on my end. I agree that the overhead downside is probably negligible, my concern is more around the predictability...

+1

this is somewhat moot, as I can't figure out how to introspect the presto version, so this is all kind of made up anyway :)

I ended up implementing the concurrent searching over the batches of `folderIds`