posit-dev / posit-dev/querychat
Add max_rows parameter to .app() for large data handling
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 212
- Forks
- 29
- Avg merge
- 22h 24m
- Merged PRs (30d)
- 27
Description
Summary
Implement a max_rows parameter on the .app() method to handle large datasets gracefully.
Background
The warn_if_large_dataframe() logic was removed in preparation for a better approach to handling large datasets. Instead of just warning developers, we should provide a configurable way to limit displayed data.
Proposed Solution
- Add a
max_rowsparameter to the.app()method - Use
.head(max_rows)on filtered data before displaying - Warn the developer (via console/logs) that not all data is shown in the app
- Provide a sensible message to the app user indicating that not all data is available (e.g., "Showing first N of M rows")
Implementation Notes
- This should be implemented after Polars and Ibis support has landed
- The
max_rowsparameter should have a sensible default (e.g., 500 rows) - The user-facing message should be clear but not alarming
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Python .app() entry point and review the existing filtered-data display path, keeping the planned Polars and Ibis support in mind. Done means .app() accepts a configurable max_rows default, limits displayed results, warns the developer, and tells the app user how many rows are shown versus available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100