You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(r/DataFrameSource): Use duckdb or SQLite (first available) (#178)
* refactor: DataFrameSource extends DBISource
* feat(DataFrameSource): Choose between duckdb and sqlite engines
* chore: Make duckdb an optional dependency
* feat: Use duckdb or sqlite based on first available
* chore(pkg-r): Avoid CRAN note about whisker
* ci(pkg-r): Don't check-depends-only
* chore: Add NEWS item
Copy file name to clipboardExpand all lines: pkg-r/NEWS.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,7 @@
1
1
# querychat (development version)
2
2
3
+
*`querychat()` and `QueryChat$new()` now use either `{duckdb}` or `{SQLite}` for the in-memory database backend for data frames, depending on which package is installed. If both are installed, `{duckdb}` will be preferred. You can explicitly choose the `engine` in `DataFrameSource$new()` or set `querychat.DataFrameSource.engine` option to choose a global default. (#178)
4
+
3
5
*`QueryChat$sidebar()`, `QueryChat$ui()`, and `QueryChat$server()` now support an optional `id` parameter to enable use within Shiny modules. When used in a module UI function, pass `id = ns("your_id")` where `ns` is the namespacing function from `shiny::NS()`. In the corresponding module server function, pass the unwrapped ID to `QueryChat$server(id = "your_id")`. This enables multiple independent QueryChat instances from the same QueryChat object. (#172)
4
6
5
7
*`QueryChat$client()` can now create standalone querychat-enabled chat clients with configurable tools and callbacks, enabling use outside of Shiny applications. (#168)
0 commit comments