Paginate SQL insights in Slack subscription
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Description
Feature request
Is your feature request related to a problem?
SQL insights with large amounts of data aren't rendered nicely in a Slack subscription. Example: An insight of survey results that is already filtered for the last 24h, but there is still too much data coming in.
Describe the solution you'd like
Use the Slack block API to paginate and/or filter the results of the subscription.
Describe alternatives you've considered
Display only the latest data in the subscription.
Additional context
Related support ticket: https://posthoghelp.zendesk.com/agent/tickets/33855 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/37154)
Contributor guide
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 by locating the SQL insights Slack subscription flow and the code that renders its results as Slack blocks; no file or test is named in the issue. Check the Slack Block API limits and trace a large result through the subscription. Done means large SQL insights can be paginated and/or filtered in Slack without relying on showing only the latest data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100