Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Should `versionsuffix` be required with the canonical names feature?

未关闭
#735 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
42/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
活跃
技术栈
markdown, wasm
领域
documentation

调研方向

Start by reading the two existing comments to see whether maintainers have already leaned toward a decision, since this is framed as an open spec question rather than a task. Then locate the spec sections defining canonical names, versionsuffix and WIT version rendering in the component-model specification, and check how (component (import "a:b/c@1" (interface))) is currently validated. Done looks like an agreed-upon spec wording change (or a documented decision not to change it) covering whether a full semver is always required.

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

描述

I believe that right now as-is the spec considers this component valid: (component (import "a:b/c@1" (interface))) -- specifically it's got a canonical version but the versionsuffix isn't present. This doesn't translate well to WIT, however, because the full version isn't present. Additionally when generating a component the WIT full version should always be presented, so I wanted to ask -- should the spec be changed here? Specifically should a full valid semver always be required, meaning that if a canonical name were used that a versionsuffix would be required?

主要语言
WebAssembly
星标
1.4k
派生
132
平均合并
3 天 14 小时
30 天内合并 PR
12

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

WebAssembly/component-model 的其他 Issue

查看 WebAssembly/component-model 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 发到你的邮箱

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