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
Copy file name to clipboardExpand all lines: pkg-py/docs/build.qmd
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ If you have an existing app with a reactive data frame that flows through multip
26
26
Integrating querychat into a Shiny app requires just three steps:
27
27
28
28
1. Initialize a `querychat()` instance with your data
29
-
2. Add the querychat UI component (either `.sidebar()` or `.ui()`)
29
+
2. Add the UI component (either `.sidebar()` or `.ui()`)
30
30
3. Use reactive values like `.df()`, `.sql()`, and `.title()` to build outputs that respond to user queries
31
31
32
32
Here's a starter template demonstrating these steps:
@@ -279,8 +279,8 @@ This is equivalent to the user asking the LLM to "reset" or "show all data".
279
279
280
280
Currently, you have two options for exploring multiple tables in querychat:
281
281
282
-
1. Join the tables into a single table before passing to QueryChat
283
-
2. Use multiple QueryChat instances in the same app
282
+
1. Join the tables into a single table before passing to querychat
283
+
2. Use multiple querychat instances in the same app
284
284
285
285
The first option makes it possible to chat with multiple tables inside a single chat interface, whereas the second option requires a separate chat interface for each table.
286
286
@@ -290,7 +290,7 @@ The first option makes it possible to chat with multiple tables inside a single
290
290
We plan to support multiple filtered tables in a future release -- if you're interested in this feature, please upvote [the relevant issue](https://github.com/posit-dev/querychat/issues/6)
291
291
:::
292
292
293
-
Here's an example of the second approach, using two separate QueryChat instances to explore both the `titanic` and `penguins` datasets within the same app:
293
+
Here's an example of the second approach, using two separate querychat instances to explore both the `titanic` and `penguins` datasets within the same app:
0 commit comments