feat(tools): add Markdown export alongside DOCX - #80
Merged
Conversation
Export already assembled the entire report as a Markdown string and only then handed it to the DOCX converter, so exporting .md is that same string written straight to disk rather than a second render path. The Save button now opens a format menu instead of exporting on click. Both formats carry identical content from the same summarize call, so choosing Markdown costs no extra credits. Model output keeps its fenced code blocks and lists verbatim in .md, which the converter flattens. buildExportMarkdown and generateExportFilename move to an electron-free utils module. That is what makes them reachable from test/run.mjs: tools.service.ts imports `dialog`, which the test stub does not provide, so anything left in that module cannot be loaded outside Electron. generateExportFilename branches on `md` and lets everything else fall through to docx. `format` arrives over IPC from the renderer, where the type annotation is erased, so an unexpected value must not reach the file extension. The DOCX conversion now runs after the save dialog rather than before. Cancelling no longer pays for a conversion nobody uses, and a Markdown export never pays for it at all. Output is unchanged. Docs in marketing-website and backend still name DOCX as the only format and need matching updates in their own repos. Closes #79 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Formatting the touched files also rewrapped two auth signatures that have nothing to do with export. Prettier is not enforced here and a number of files do not satisfy it, so reformatting pre-existing violations just to sit next to a change puts unrelated hunks in front of a reviewer. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
DropdownMenuContent portals into the overflow-hidden <main> from main-frame, not document.body. The control panel is the bottom-most thing in it, so a downward menu opens past that edge and is clipped - not merely flipped by collision detection, which is what the previous wording implied and what would invite someone to drop the prop. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
@-