feat(playtest): redesign global asset gallery - #313
Open
huyanxius wants to merge 12 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
审查结论
完整检查了固定差异中的预览台全局造型画廊、项目筛选与分页读取、可播放动作/帧统计、共享 EditorialEntryCard、项目中心预览,以及认证产品页的共享色彩令牌迁移。相关调用方与工作台模型保持一致,未发现达到反馈阈值的正确性、可访问性或兼容性回归。
验证方面,git diff --check 8821b192c43700083850559eadf7419950c96abc...9b1d808227013ef80e1df1aae79a588cacc4dc53 通过。挂载工作区未安装 node_modules,因此本次无法重新执行 Vitest 与 TypeScript typecheck(vitest/tsc 不可用)。
This was referenced Aug 14, 2026
The project center needs a calmer asset-first browsing surface. Render the create entrance, project previews, and empty pixel canvases while resolving real character preview images. Existing project creation, deletion, pagination, and navigation behavior stays intact.
The redesigned gallery must keep its real API and navigation boundaries explicit. Cover character preview requests, empty canvases, creation links, deletion, and pagination. The tests now assert user-visible behavior instead of styling internals.
The workspace heading needs the same concise context used across the product surfaces. Add the approved tagline directly beneath the existing page title. No workspace navigation or data-loading behavior changes.
The approved workspace context line should remain part of the rendered heading area. Assert the tagline alongside the existing navigation behavior. The focused coverage protects the copy without expanding workspace scope.
huyanxius
force-pushed
the
feat/304-playtest-gallery
branch
from
August 14, 2026 09:00
9b1d808 to
c9f7524
Compare
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
Codecov exposed untested project preview fallback branches. Exercise reference images, first frames, and isolated request failures. Keep gallery previews resilient without changing production behavior.
Project and Playtest entries need the same visual behavior without duplicated styling. Extract the editorial entry card with asset-specific artwork and reuse it for project creation. Both entry points now share sizing, color, tilt, and hover behavior.
The project creation entry must keep its established artwork and accessible link contract. Assert that the rendered link comes from the shared editorial entry component. The test protects the project entry while Playtest reuses the same component.
The global Playtest entry should surface real outfits before decorative scene content. Replace the hero with a filterable cross-project gallery and reuse the shared empty-state entry card. Cards now expose project context, playable actions, frame totals, and disabled states.
The entry must preserve routing, filtering, pagination, empty states, and truthful playback metadata. Cover the gallery states and add a zero-frame action fixture that must stay out of playable summaries. The regression protects both the frozen layout and the workbench playback contract.
Reviewers need stable visual evidence for the frozen Playtest entry design. Add desktop and narrow-screen captures of the populated global outfit gallery. The images document the responsive states used for Issue 304 acceptance.
Zero-frame actions are visible metadata but cannot enter Playtest. Count only actions with real frames in the Workspace outfit summary. Keep the displayed action total aligned with the playable frame contract.
huyanxius
force-pushed
the
feat/304-playtest-gallery
branch
from
August 14, 2026 09:33
c9f7524 to
cc64fa9
Compare
The shared asset fixture now includes one zero-frame draft action. Expect character detail and asset library views to render all three actions. Align both tests with the existing asset display behavior.
huyanxius
force-pushed
the
feat/304-playtest-gallery
branch
from
August 14, 2026 09:38
cc64fa9 to
0ae5a3b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
本 PR 将全局预览台收敛为紧凑的跨项目造型画廊,并让项目创建入口与预览台空态复用同一套编辑式入口卡。依赖 #299;其合并后本 PR 将收敛为 #304 的独立增量。
Why
原
/playtest以装饰性点阵场景和大型项目分区为主,真实可操作资产进入首屏较晚,卡片也缺少项目、动作摘要与可用状态。预览台需要延续项目中心、创作页和工作台的共享视觉语言,同时保持跨项目快速启动的单一职责。Changes
EditorialEntryCard,项目创建入口与预览台空态共享尺寸、圆角、配色、倾斜和 hover 逻辑;两处使用各自素材。Implementation
Verification
npm test -- src/pages/projects/index.test.tsx src/pages/playtest/entry.test.tsx:2 个测试文件、8 项测试通过。npm run typecheck:通过。npx oxfmt --check <changed-files>:涉及文件格式检查通过。npx oxlint <changed-files>:涉及文件静态检查通过。npm run build:通过。git diff --check:通过。Screenshots
Desktop
Mobile
Scope
Related Issues
Closes #304
Refs #299
Refs #274