prioritize prototypes in Community filters - #6980
Conversation
Generated-By: looper 0.11.8 (runner=fixer, agent=codex)
nettee
left a comment
There was a problem hiding this comment.
@Siri-Ray I verified that the Community gallery now orders Prototype before Slides, initializes the Prototype facet, and that the updated regression fixtures preserve explicit Slides coverage for deck-only catalogs. The live PR checks are green across the changed web surface. This is a focused, well-covered improvement to the intended prototype-first discovery flow—nice work!
🔁 Powered by Looper · runner=reviewer · agent=codex · An autonomous AI dev team for your GitHub repos.|
🧪 This PR has changes that need a manual QA pass before merge — please hold off self-merging for now; we'll loop QA in once it's merge-ready (and design/product have signed off, where applicable). |
ivy-ting
left a comment
There was a problem hiding this comment.
Thanks for the contribution. I completed QA validation for this PR.
QA found a blocking catalogue fallback regression: when the available catalogue contains Slides but no Prototype templates, Community renders the Slides tab but keeps Prototype as the active type. No tab is active and the card grid is empty until the user manually clicks Slides. A focused regression check reproduces this consistently.
Please fall back to the first available template type when Prototype is absent, and add coverage for a catalogue without Prototype templates.
Conclusion: Not accepted.
Generated-By: looper 0.11.8 (runner=fixer, agent=codex)
|
Looper fixer round complete — 8dc65af
🔁 Powered by Looper · runner=fixer · agent=codex · An autonomous AI dev team for your GitHub repos. |
|
Thanks for the contribution. I completed QA validation for the latest head QA Acceptance Record Scope:
Scope-to-evidence:
Verified:
Not verified:
Risks / notes:
Conclusion:
|
|
Successfully created backport PR for |
* prioritize prototypes in Community filters * test(web): select slides in modal mapping coverage Generated-By: looper 0.11.8 (runner=fixer, agent=codex) * fix(web): fall back to an available Community facet Generated-By: looper 0.11.8 (runner=fixer, agent=codex) * test(web): select slides before deck preview assertion --------- (cherry picked from commit e711d11) Co-authored-by: Ray Xi <2667192167@qq.com> Co-authored-by: Amy <1184569493@qq.com>













































Why
The Community template gallery currently leads with Slides even though Prototype is the preferred first creation type. This makes the category order inconsistent with the intended prototype-first discovery flow and opens the gallery on slide templates by default.
This PR aligns the Community entry experience with the requested priority while keeping the existing catalogue, filtering, template actions, and routing unchanged.
What users will see
Community now opens with Prototype selected first and Slides immediately second. The initial card grid and subtype filters show prototype templates; selecting Slides continues to show the same slide catalogue and actions as before.
Surface area
apps/weborapps/desktop(including Electron menu bar)odsubcommand or flag, newtools-dev/tools-packflag, or newOD_*env var/api/*endpoint, new SSE event, or changed shape inpackages/contractsskills/,design-systems/,design-templates/, orcraft/, or change to the skills protocolTRANSLATIONS.mdfor the locale workflow)package.json(dependenciesordevDependencies); workspace-packagepackage.jsonfiles are out of scope. Include a paragraph on what we get vs. what bytes we ship (seeCONTRIBUTING.md→ Code style)Screenshots
Omitted at the request of the change author. The visible category order and initial active gallery are covered by the focused Community regression test.
Bug fix verification
This is a preference-ordering change rather than a bug fix. The public Community behavior is covered in
apps/web/tests/community-view.test.tsx: the new prototype-first assertion failed before the source change and passes on this branch.Validation
pnpm --filter @open-design/web exec vitest run -c vitest.config.ts tests/community-view.test.tsx --maxWorkers=2— 17 tests passedpnpm --filter @open-design/web typecheckpnpm guardpnpm typecheckgit diff --check origin/main...HEAD