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

.ets (ArkTS) files have no AST extractor — HarmonyOS sources silently absent from the graph

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
65/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
devtools

调研方向

Start at the AST extraction pass and the existing TypeScript extractor, then check how .ets extensions are classified and dispatched. Use the tree-sitter TypeScript grammar coverage described in the issue, including ArkTS decorators and structs, and compare extraction on a HarmonyOS sample. Done means .ets files contribute AST nodes or the REPORT explicitly records unsupported extensions.

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

描述

Same class as #1689 (.r), different language: .ets (ArkTS, HarmonyOS) is classified as code by detect but has no AST extractor.

Repro (graphify 0.x via uv, 2026-09-23):

  1. Point graphify at a repo containing .ets sources (e.g. a HarmonyOS host app: ArkTS UI + NAPI glue).
  2. Run the AST extraction pass.

Measured: 20 .ets files detected as code, all skipped:

warning: 20 file(s) are classified as code but graphify has no AST extractor for their language, so they contributed nothing to the graph: .ets (20). Please open an issue to request support for these (#1689).

The final graph (5,285 nodes over a ~537-file curated corpus) has zero nodes from the HarmonyOS host — a whole platform missing from an architecture analysis, with only a warning line to show for it.

Ask: an ArkTS extractor. ArkTS is a TypeScript derivative (HarmonyOS); the TS tree-sitter grammar covers most of it — .ets may be as simple as mapping onto the existing TS extractor, with a fallback for ArkTS-specific decorators/structs (struct Foo {\@State ...\}). If full support is far off, consider emitting the missing-extension list in the REPORT (not only stderr) so 'graph is complete' claims stay honest.

主要语言
Python
星标
124k
派生
11.9k
PR 合并指标
30 天内没有已合并 PR

环境准备

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

从这里开始

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

Graphify-Labs/graphify 的其他 Issue

查看 Graphify-Labs/graphify 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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