when I go through activities and am on a commit, in the preview to the right JSON shows up where I would expect file information. the json has the file information inside, so it is generally looking at the right stuff, but it is not formatting it.
when I go through activities and am on a commit, in the preview to the right JSON shows up where I would expect file information. the json has the file information inside, so it is generally looking at the right stuff, but it is not formatting it.
hugo
added this to the first feature complete release milestone 2026-08-03 20:56:21 +00:00
hugo
added the bug label 2026-08-03 20:56:21 +00:00
Added a shared compatibility parser for Forgejo/Gitea commit activity payloads, including mixed-case Commits, HeadCommit, and Len fields.
Replaced raw JSON in the TUI Home preview with a Markdown-rendered commit count and readable rows containing each short hash, message, author, and timestamp.
Preserved comment and non-commit activity previews; opening the activity still routes to the head commit and its changed-file list.
Updated TESTING.md and added regression coverage at both the activity parser and TUI presentation boundaries.
Live terminal check against the configured Forgejo server: selected the pushed commit activity, confirmed the formatted count/hash/message/author/timestamp with no JSON, then opened it and confirmed the changed-file list.
This is a TUI issue, so no iPhone release build or deployment was performed, as requested.
Implemented in `61e96cc`.
- Added a shared compatibility parser for Forgejo/Gitea commit activity payloads, including mixed-case `Commits`, `HeadCommit`, and `Len` fields.
- Replaced raw JSON in the TUI Home preview with a Markdown-rendered commit count and readable rows containing each short hash, message, author, and timestamp.
- Preserved comment and non-commit activity previews; opening the activity still routes to the head commit and its changed-file list.
- Updated `TESTING.md` and added regression coverage at both the activity parser and TUI presentation boundaries.
Verification:
- `cargo fmt --all -- --check`
- `RUSTFLAGS="-D warnings" cargo check --workspace --all-targets`
- `cargo clippy --workspace --all-targets -- -D warnings`
- `cargo test --workspace` (48 passed)
- Live terminal check against the configured Forgejo server: selected the pushed commit activity, confirmed the formatted count/hash/message/author/timestamp with no JSON, then opened it and confirmed the changed-file list.
This is a TUI issue, so no iPhone release build or deployment was performed, as requested.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
when I go through activities and am on a commit, in the preview to the right JSON shows up where I would expect file information. the json has the file information inside, so it is generally looking at the right stuff, but it is not formatting it.
Implemented in
61e96cc.Commits,HeadCommit, andLenfields.TESTING.mdand added regression coverage at both the activity parser and TUI presentation boundaries.Verification:
cargo fmt --all -- --checkRUSTFLAGS="-D warnings" cargo check --workspace --all-targetscargo clippy --workspace --all-targets -- -D warningscargo test --workspace(48 passed)This is a TUI issue, so no iPhone release build or deployment was performed, as requested.