State modelのリファクタ - #26
Conversation
|
Warning Review limit reached
Next review available in: 55 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (11)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 197fd74995
ℹ️ 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".
| (assoc state' :buffers (if exists? | ||
| updated-bufs | ||
| (conj updated-bufs buf))))) | ||
| (:frame state') (update :frame window/assoc-selected-buffer buf)))) |
There was a problem hiding this comment.
Synchronize every window showing the edited buffer
When two windows display the same buffer, this updates only the selected leaf. After editing in that window, selecting the other window retrieves its stale buffer snapshot, and select-window passes that snapshot back through assoc-current-buffer, overwriting both :current-buffer and the matching entry in :buffers; recent edits therefore disappear when moving between windows. Update every window referencing the buffer, or store a shared stable buffer reference instead of independent buffer values.
Useful? React with 👍 / 👎.
No description provided.