agent-substrate / agent-substrate/substrate

Actor Template labels

未关闭
#1,615 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
area/api kind/feature
主要语言
Go
星标
1.9k
派生
317
平均合并
1 天 23 小时
30 天内合并 PR
289

描述

Hi. Our pre-release substrate integration ended up depending on actor template labels. We used them for apis and user surfaces to understand things like the purpose, runtime, or capabilities an actor template provided. We are wondering if labels will return to actor templates in future revisions in order to plan our upgrade path. If you have a recommended way to achieve the same functionality today we would appreciate that too. Thanks!

贡献指南

打开贡献指南

调研方向

No concrete files, tests, or entry points are mentioned. Start by checking the project documentation for actor templates and API/contract references that discuss template labels or migration notes, then trace any referenced implementation area that handles actor-template metadata. A good outcome is either a maintainer-confirmed roadmap/decision in the issue or a docs update stating whether labels are coming back and the supported alternative for current users.

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

评估

技术栈
go
领域
backend-api-design
Issue 类型
功能
难度
4/5
预计耗时
3-5 天
活跃度
活跃
描述清晰度
需要澄清
新手友好度
30/100

把新 issue 发到你的邮箱

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