The schema does not say whether a type has a preview template, so the admin mints a token to learn it

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
54/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
csharp, openapi

调研方向

Start by tracing the Management API's GET /schema response and how it derives the existing localizable and searchable fields. Check how PreviewSettings identifies templates and how permission checks affect preview token minting; acceptance requires previewable to reflect setting changes and return false when the caller lacks permission. Then update the OpenAPI document and both generated clients, and verify the response and client schemas.

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

描述

area:api area:publishing type:feature

Problem

The admin cannot tell whether a content type has a preview template without minting a preview token. The templates are a setting of the site (PreviewSettings), and GET /schema says nothing about them, so the content form mints a token on every read and every save of any type to learn it (#3403, from the review of #3401). A preview token cannot be revoked, so each of these mints is a credential nobody asked for.

Proposal

Say on each type of the Management API's GET /schema whether the site has a preview template for it, as a boolean named previewable, in the style of localizable and searchable, which the admin already reads (#3437), narrowed as the rest of the answer is (a caller who may not mint a preview token for the type gets false). It adds to an answer and changes no model. The OpenAPI document and the generated clients take the member.

Until it is merged the admin mints only when the preview pane opens, for any type, and reads the member when it is there (#3403).

Acceptance

  • GET /schema says for each type whether the site has a preview template for it, and follows a change of the setting
  • A caller who may not mint a preview token for the type reads false
  • The OpenAPI document and the two clients have the member

For workstation B (#3356). Asked for by #3403.

主要语言
C#
星标
567
派生
107
平均合并
1 小时 19 分钟
30 天内合并 PR
353

环境准备

从这里开始

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

fluentcms/FluentCMS 的其他 Issue

查看 fluentcms/FluentCMS 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

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