Document period field on DocumentInsight rollups#27
Merged
Conversation
Recent activity is now returned as daily rollups while older activity is aggregated into weekly rollups, exposed via a new period enum on the response payload.
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.
Summary
Updates the
DocumentInsightresponse schema to document the newperiodfield added in outline/outline#12113.Recent activity is returned as daily rollups, while older activity is aggregated into weekly rollups. The new
periodenum (day|week) on each rollup tells consumers which bucket a row represents. Thedatefor weekly rollups represents the first day (Monday) of the week.Also tweaks the
/documents.insightsendpoint description to reflect that returned rollups may now be daily or weekly.Survey of other recent merges
Checked the other PRs merged in outline/outline since 2026-05-17 for relevance to the public API surface; none required spec updates:
getJWTToken→getSessionToken) — internal renameimports.createandcollections.import, neither of which is currently documented in this specTest plan
yarn validatepasses (Spectral + operation IDs)spec3.jsonfromspec3.ymlGenerated by Claude Code