Scott Chamberlain

Query-able fields?

9

@cboettig what fields should users be allowed to query? since you're more familiar with the data... Right now, I've set it up so that users can query on any field....

Change to new cran checks badge URL

1

👋🏽 I maintain the cran checks badges. Please change to the new cran checks badge URL (e.g., `https://badges.cranchecks.info/worst/dplyr.svg`). Old badges at (e.g. `https://cranchecks.info/badges/worst/dplyr`) will be unavailable as of Jan 1st...

Change to new cran checks badge URL

1

👋🏽 I maintain the cran checks badges. Please change to the new cran checks badge URL (e.g., `https://badges.cranchecks.info/worst/dplyr.svg`). Old badges at (e.g. `https://cranchecks.info/badges/worst/dplyr`) will be unavailable as of Jan 1st...

datapkg_read() - allow github user/repo specification for path parameter

1

not sure if this makes sense, i don't know whether a lot of datasets will be on github or not, if not, then may not make sense

Persist datasets locally?

3

I wonder if it makes sense to persist datasets on a user's machine. And then read the cached version unless user wants to update, or possibly check if any changes...

e.g., ``` r index("shakespeare") %>% query("prefix", speaker = "we") ``` as an alternative to ``` r index("shakespeare") %>% prefix(speaker = we) ```

basically `toggle=FALSE` on the pipe helpers

https://travis-ci.org/ropensci/elasticdsl/jobs/116706796#L4219

function for explaining what query will be performed

4

in readme, we have `explain()`, but doesn't exist yet (and conflicts with `dplyr::explain()`), working on `describe()` right now...