New Edit Content: the Preview action on a History version does nothing

未关闭
#38,653 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
56/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
frontend

调研方向

Start with core-web/libs/edit-content/src/lib/store/features/history/history.feature.ts at the PREVIEW case, then compare how the legacy editor previews a version and review the design decision in #38033. Trace which content types have a preview target and where the History action is rendered; add coverage for dispatch and hiding the action. Done means preview opens the selected version as agreed and types without a target no longer show Preview.

由索引模型根据 Issue 内容生成。

描述

dotCMS: New Edit Contentlet Team : Scout Type : Defect
Problem Statement

Each version in the History timeline offers a Preview action. Clicking it has no effect: the store handles the action with an empty case marked as a TODO. Authors expect it to open the version's rendered page, as the legacy editor does from its version list.

Steps to Reproduce
  1. Open a contentlet with several versions in the new editor; open the History tab.
  2. Open the actions menu of any version and click Preview.

Expected: the version is previewed (the rendered page for page or URL-mapped content, or the detail view for other content). Actual: nothing happens, no error.

Acceptance Criteria
  • Preview opens the selected version in the same way the legacy editor previews a version, in a new tab or panel as agreed with design in #38033.
  • Content types with no preview target hide the action instead of showing a dead one.
  • Spec covers the dispatch and the hidden case.
dotCMS Version

main (2026-11-18)

Severity

Minor

Links
  • #38634 pillar; #38033 redesign
  • Code: core-web/libs/edit-content/src/lib/store/features/history/history.feature.ts:693 (PREVIEW case, TODO)
主要语言
Java
星标
972
派生
493
平均合并
2 天 12 小时
30 天内合并 PR
228

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

dotCMS/core 的其他 Issue

查看 dotCMS/core 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。