39 lines
1.7 KiB
Markdown
39 lines
1.7 KiB
Markdown
# TODO
|
|
|
|
The read-only model now includes paginated review threads and comments, PR
|
|
conversation comments, submitted reviews, individual checks, branch-protection
|
|
requirements, rulesets, merge queues, deployment requirements, viewer
|
|
capabilities, head SHA, persistent unread updates, offline cache fallback,
|
|
commit/force-push history, and paginated checks and annotations.
|
|
The following read-only improvements remain before or alongside write support.
|
|
|
|
## Workflow and navigation
|
|
|
|
- Open the current PR, comment, review, check, or source location in a browser.
|
|
- Copy URLs, commit SHAs, file paths, and rendered comment text to the
|
|
clipboard.
|
|
- Add navigation for the next thread by status or author, not only the next
|
|
unread update.
|
|
- Remember the selected PR, thread, scroll position, pane width, and folded
|
|
state between runs.
|
|
- Audit screen-reader behavior beyond the new no-color and high-contrast modes.
|
|
|
|
## Data completeness and resilience
|
|
|
|
- Model pending reviews, minimized comments, deleted comments, and explicit
|
|
reply relationships.
|
|
- Show rate-limit remaining/reset information and distinguish it from network
|
|
or permission failures.
|
|
- Support retrying individual failed pages while retaining clearly marked
|
|
partial data, rather than failing the entire refresh.
|
|
- Add fixture coverage for GitHub Enterprise Server schema differences, team
|
|
reviewers, deleted users, very large PRs, and mixed legacy status contexts.
|
|
|
|
## Preparation for write support
|
|
|
|
- Fetch per-comment update/delete permissions and the exact reply target IDs.
|
|
- Define head-SHA conflict handling for comments and suggestions composed
|
|
against an older revision.
|
|
- Design confirmation and optimistic-update behavior for resolving threads,
|
|
submitting reviews, and applying suggestions.
|