Skip to content

Improve Wiki reader layout and revision history UX - #2547

Merged
lyingbug merged 1 commit into
Tencent:mainfrom
lyingbug:feat/wiki-reader-ui-revision-history
Aug 5, 2026
Merged

Improve Wiki reader layout and revision history UX#2547
lyingbug merged 1 commit into
Tencent:mainfrom
lyingbug:feat/wiki-reader-ui-revision-history

Conversation

@lyingbug

@lyingbug lyingbug commented Aug 5, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Restructure the Wiki reading page header: title on the left, actions and timestamp on the right, and metadata badges (type, version, edit source, aliases) on a single row below the title.
  • Rework the revision history drawer with resizable SettingDrawer, field-level diffs (title/summary/body), and corrected incremental comparison (previous → selected); v1 now shows initial creation content instead of an empty state.
  • Unify the page footer (backlinks + source documents) with in-body wiki link styling and clearer spacing between multiple items.
  • Fix empty-string line diffing so v1 title/summary diffs no longer show spurious red blank lines.

Test plan

  • Open a Wiki page and verify header layout: badges row, right-side actions, and alias badges.
  • Enter edit mode and confirm title/summary/content fields are visually distinct with bordered inputs.
  • Open revision history: compare v2+ incremental/cumulative/raw modes; select v1 and confirm "版本变更" shows initial content without empty delete rows.
  • Verify footer backlinks and source docs are clickable, spaced apart, and use dashed wiki-link styling.
  • Run npm test -- src/utils/wikiLineDiff.test.ts src/utils/wikiRevisionDiff.test.ts

Restructure the page header and footer for clearer metadata, add field-level revision diffs with correct incremental comparison (including v1 initial content), and align footer links with in-body wiki link styling.
@lyingbug
lyingbug merged commit 63b5f35 into Tencent:main Aug 5, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant