Conversation
Author
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a “30 days ago” snapshot (month_ago) to the analytics payload and updates the integrations table UI to show ±Installations and ±Position deltas based on that snapshot.
Changes:
- Worker: looks up the history KV entry closest to 30 days ago and stores it as
AnalyticsData.month_ago. - Worker: preserves
month_agothrough analytics schema migrations and updates schedule handler tests accordingly. - Site: conditionally renders two new comparison columns on the integrations table (and supports custom table headers in the shared table layout).
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| worker/src/handlers/schedule.ts | Populates storedAnalytics.month_ago by listing history keys and reading the closest snapshot. |
| worker/src/utils/migrate.ts | Preserves month_ago field across analytics data migrations. |
| worker/src/data.ts | Adds MonthAgoData type and optional month_ago field on AnalyticsData. |
| worker/tests/handlers/schedule.spec.ts | Extends PROCESS_QUEUE test to mock history list/get and assert month_ago is written. |
| site/src/integrations.html | Adds conditional UI to show ±Installations / ±Position vs month-ago snapshot. |
| site/src/_layouts/table.html | Allows pages to override the table header via customTableHeader. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Add 30-day comparison columns to integrations table
What
Two new columns on the integrations page: ± Installations and ± Position, showing how each integration changed compared to ~30 days ago.
Why
Makes it easy to measure the impact of changes across releases — e.g. after adding new discovery for UniFi Protect, UniFi Access and UniFi Network, you can immediately see how their install numbers and ranking evolve over the following month.
How it works
month_agoinside the existingAnalyticsDataobjectmonth_ago.integrationsinto the page at build time; all comparison logic runs client-sidemonth_agodata exists yet (first deployment) the columns are simply hidden until history is available