Add Overleaf review comment management commands#25
Open
shiquda wants to merge 1 commit into
Open
Conversation
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
This PR adds CLI support for managing Overleaf review comments.
New commands:
olcli comments list [project]olcli comments add <file> <message> [project]olcli comments resolve <threadId> [project]olcli comments reopen <threadId> [project]olcli comments delete <threadId> [project]comments listincludes source file, line/column, selected text, messages, status, and optional source context via--context. It also supports status filtering with--status open|resolved|alland JSON output via--json.comments addcan attach a comment to selected text using--text, or to an explicit source range using--line/--column/--lengthor--position/--length.Implementation Notes
The implementation mirrors Overleaf's web editor behavior:
/project/:projectId/threadsto retrieve thread messages and resolved state.Validation
npm run build.npm test --if-present(no test script is currently configured).npm pack --dry-run.Note:
npm run lintis not currently runnable in this repository as-is because the package has a lint script but no ESLint dependency/config. I tested this separately and did not include lint setup in this PR to avoid mixing unrelated lint configuration and existing style cleanup into the feature change.