Document addon configuration fields for Replicator/Bard sets
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 25/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
调研方向
The API is proposed in statamic/cms#15422, a draft that is not merged, so the docs cannot be verified against shipped code yet. Read that PR for Statamic\Fieldtypes\Sets::appendSetConfigField() and appendSetConfigFields(), then cover the checklist in the issue body. Done means a docs page that separates set configuration from per-block fields and includes single, grouped and multiple-field examples, and wait for the API to be accepted before finalising.
由索引模型根据 Issue 内容生成。
描述
Companion tracking issue for the proposed API in statamic/cms#15422. The PR is a draft and has not been merged.
The change adds Statamic\Fieldtypes\Sets::appendSetConfigField($handle, $config) and appendSetConfigFields($fields) to register native configuration fields in the Edit Set stack for Replicator and Bard.
Documentation should distinguish reusable set configuration in a blueprint/fieldset from fields stored on individual content blocks. For example, an addon can register an editorial note or a native group of guidance fields. The values are saved alongside that set's native configuration.
Suggested coverage once the API is accepted:
- Register fields during a service provider's boot phase, using keyed native field definitions.
- Single-field and multiple-field examples, including a
groupfor namespaced nested configuration. - Native preprocessing, metadata, validation, and processing apply. Validation is enforced when applying/saving the containing field.
- Edit Set's Confirm button updates the containing field editor; save the field and blueprint/fieldset to persist changes.
- Native set keys are reserved. Use addon-specific handles.
- Existing custom metadata remains intact when its addon is not registered.
The extension is generic; no AI-specific settings are added to core.
- 主要语言
- PHP
- 星标
- 133
- 派生
- 405
- 平均合并
- 21 小时 45 分钟
- 30 天内合并 PR
- 12
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
statamic/docs 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 75/100
维护者通常 1 天内回复
-
Chunked Uploads未关闭
难度 1/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
Installation / Deployment Guides
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 40/100
维护者通常 1 天内回复
-
Document how conditions treat empty and null values可能已有人在做 @joshdaugherty 于 11 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 25/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 2 天内回复
-
bug
难度 1/5 1 小时以内 新手友好度 85/100
-
难度 2/5 1-3 小时 新手友好度 63/100
smarty-php/smarty#1215 ·
-
sync-en
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
sync-en
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 4 天内回复