Repository navigation
feat(insights): add export - #122
Conversation
Build a portable report from the compact dashboard with exact token counts and no rescan. Cover the report shape, cache scope, empty data, and table escaping.
Put Export between Refresh and Settings with As Markdown as its first action. The menu sizes to its content from shared layout tokens, and export writes the prepared dashboard through the folder picker.
[Medium impact] The PR reaches the local Insights dashboard and its export workflow. The PR appears safe to merge, with a non-blocking issue where export can use the previous selection. Findings
SummaryAdds Markdown export from the prepared Insights dashboard.
Reviews (1) · Last reviewed commit: "chore(insights): remove unused helpers a..." · Reviewed by Greptile |
| if (this.closed || !this.dashboard || this.exporting || this.busy()) return; | ||
| const now = new Date(); | ||
| const markdown = dashboardMarkdown(this.dashboard, { now }); |
There was a problem hiding this comment.
Export uses the previous selection
After a user changes the period, provider, model, or selected day, scheduleDashboard keeps the old dashboard until the new report is ready. busy() stays false during that wait, so export can save the previous selection while the controls show the new one.
Disable export while an update is pending or queued, and check that dashboardKey matches the current options before exporting.
Uh oh!
There was an error while loading. Please reload this page.