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

Explicit structuring

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
领域
compilers

调研方向

Start with the linked meta-transport forum post and compare the fixed port-ID approach with the proposed underscore or leading-dot DSDL names shown in the issue. No files or tests are named; done would require an agreed representation and corresponding specification updates.

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

描述

enhancement

As mentioned in the post about meta-transport, highly hierarchical definitions are hard to view because the representation of namespace members is inherently flat which does not reflect the data structure.

Fixed port-IDs make top-level types very salient. It is also natural since a nested type does not need to have a fixed port-ID. This solution is unavailable for top-level types that don't have a fixed port-ID, such as in the linked case; an alternative is to simply add a special character pattern, such as an underscore, in place of the fixed port-ID. For example, a DSDL file Frame.1.0.uavcan would become _.Frame.1.0.uavcan. Example:

image

Alternatively, non-top-level types could be named starting with . like .Error.1.0.uavcan. That would make them hidden on Unix-like systems which is interesting.

These are very easy to implement but they are probably not the best possible solutions; other suggestions are welcome.

主要语言
没有语言数据
星标
1
派生
0
PR 合并指标
30 天内没有已合并 PR

环境准备

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

从这里开始

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

OpenCyphal/dsdl_specification 的其他 Issue

查看 OpenCyphal/dsdl_specification 的全部 Issue

相似的 Issue

更多 Compilers Issue

把新 issue 发到你的邮箱

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