Skip to content

fix: preserve file_path on comments added via web UI#9

Merged
tomasz-tomczyk merged 1 commit intomainfrom
fix/web-comment-file-path
Mar 15, 2026
Merged

fix: preserve file_path on comments added via web UI#9
tomasz-tomczyk merged 1 commit intomainfrom
fix/web-comment-file-path

Conversation

@tomasz-tomczyk
Copy link
Copy Markdown
Owner

Summary

  • document-renderer.js was passing null as the filePath argument to renderBlock for single-file reviews, so every block's dataset.filePath was set to an empty string
  • When a comment was submitted, submitNewComment sent file_path: null to the server
  • Comments with nil file_path are filtered out by the export endpoints (multi_file_comments_json), causing them to silently disappear from "Get prompt" and export responses

Fix

Store f.path as ctx.singleFilePath when the init event arrives with a single file, then pass it through to renderBlock instead of hardcoded null.

Fixes #6

@tomasz-tomczyk tomasz-tomczyk merged commit d085a1d into main Mar 15, 2026
1 check passed
@tomasz-tomczyk tomasz-tomczyk deleted the fix/web-comment-file-path branch March 15, 2026 00:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Comments added via web UI have nil file_path

1 participant