-
Notifications
You must be signed in to change notification settings - Fork 6.9k
feat(tui2): copy tui crate and normalize snapshots #7833
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
0a7bf1a to
41151be
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ 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".
7ef2836 to
bfc9b6a
Compare
|
Introduce a full codex-tui source snapshot under the new codex-tui2 crate so viewport work can be replayed in isolation. This change copies the entire codex-rs/tui/src tree into codex-rs/tui2/src in one atomic step, rather than piecemeal, to keep future diffs vs the original viewport bookmark easy to reason about. The goal is for codex-tui2 to render identically to the existing TUI behind the `features.tui2` flag while we gradually port the viewport/history commits from the joshka/viewport bookmark onto this forked tree. While on this baseline change, we also ran the codex-tui2 snapshot test suite and accepted all insta snapshots for the new crate, so the snapshot files now use the codex-tui2 naming scheme and encode the unmodified legacy TUI behavior. This keeps later viewport commits focused on intentional behavior changes (and their snapshots) rather than on mechanical snapshot renames.
- Add `skill_load_outcome: None` to all `SessionConfiguredEvent` initializers used in tui2 tests so they compile against the new protocol definition. - Add the Windows-specific `approvals_selection_popup@windows` snapshot for codex-tui2, mirroring the existing codex-tui snapshot and keeping tui2 in sync with upstream UI text. These changes are test-only and ensure tui2 continues to build and pass its snapshot suite after upstream updates to the session configuration payload.
026b409 to
4895c1a
Compare
Windows seems to race creating the output file names. This doesn't actually appear to be used for anything (guessing it's a debug tool).
Introduce a full codex-tui source snapshot under the new codex-tui2 crate so viewport work can be replayed in isolation.
This change copies the entire codex-rs/tui/src tree into codex-rs/tui2/src in one atomic step, rather than piecemeal, to keep future diffs vs the original viewport bookmark easy to reason about.
The goal is for codex-tui2 to render identically to the existing TUI behind the
features.tui2flag while we gradually port the viewport/history commits from the joshka/viewport bookmark onto this forked tree.While on this baseline change, we also ran the codex-tui2 snapshot test suite and accepted all insta snapshots for the new crate, so the snapshot files now use the codex-tui2 naming scheme and encode the unmodified legacy TUI behavior. This keeps later viewport commits focused on intentional behavior changes (and their snapshots) rather than on mechanical snapshot renames.