chore: initial public snapshot after M15 local-only descope#1
Conversation
# Conflicts: # LICENSE
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 881c96e6e1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| try { | ||
| const now = new Date().toISOString().replace(/[:.]/g, '-'); | ||
| const extension = request.format === 'markdown' ? 'md' : request.format; | ||
| const defaultUri = vscode.Uri.file(`${workspacePath}\\mindmap-export-${now}.${extension}`); |
There was a problem hiding this comment.
Use path.join when building mindmap export default URI
The export dialog default path is constructed with a hardcoded Windows separator (\), so on macOS/Linux the filename contains a literal backslash instead of a directory boundary. In those environments, the save dialog opens with an incorrect default target/name for every mindmap export, which is a cross-platform regression for a core user flow.
Useful? React with 👍 / 👎.
| children.forEach((childId) => visit(childId, depth + 1)); | ||
| }; | ||
|
|
||
| roots.forEach((root) => visit(root.id, 0)); |
There was a problem hiding this comment.
Handle no-root graphs in Markdown mindmap export
When users create a cyclic mindmap (all nodes have incoming edges), roots becomes empty; the visibility helper already has a fallback for this case, but Markdown export still traverses only roots, so it emits no node list even though nodes are present. This produces empty/near-empty Markdown exports for valid editor states reachable via edge connections.
Useful? React with 👍 / 👎.
Summary
Verification