feat: Java record components and enum constants declare no field

オープン
#332 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
30/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
java
領域
tooling

調査の方向性

Start with openspec/specs/data-symbols/spec.md line 185, which defers Java record components and enum declarations, and confirm whether that deferral still stands before any code change. Then read the fields-beside-enum case.json near line 176 and the records-and-enums semantic case to see the expected field and type nodes. Done means the three listed mismatches match, the case.json exception is removed, and the recorded outputs for both cases are updated.

索引モデルが issue の本文から書いたものです。

説明

area:indexer enhancement priority:low spec-needed
What exists today?

Java field extraction in the Java extractor, as documented at docs/LANGUAGE-CAPABILITY-MATRIX.md line 129.

How does it behave now?

The Java extractor emits no field node for a record component or an enum constant. The semantic case testdata/semantic/development/java/records-and-enums is unsupported. The known-gap case testdata/semantic/development/java/fields-beside-enum lists three mismatches: p/Order.java/Order.State/field/CLOSED@9:4, p/Order.java/Order.State/field/OPEN@8:4 and p/Order.java/Order/enum/State@7:7.

The exception for that case (case.json line 176) cites #239, which PR #330 closes.

openspec/specs/data-symbols/spec.md line 185 keeps Java record components and enum-specific declarations outside the current change.

How should it behave?

A record component and an enum constant each become a field node of their record or enum. An enum is emitted as a type node. The three mismatches then match, and the exception for fields-beside-enum can be removed.

What kind of improvement?

Correctness in an edge case.

Would this change existing behavior?

Yes. Record components and enum constants gain field nodes, and the recorded output of records-and-enums and fields-beside-enum changes with them.

Before submitting
  • I searched existing issues and this is not a duplicate
  • I checked that the current behavior is not a deliberate decision in openspec/specs/

The last box stays unchecked because openspec/specs/data-symbols/spec.md line 185 defers this declaration form, so it reads as a scope decision.

主要言語
Go
スター
0
フォーク
0
平均マージ
7時間 42分
マージ済み PR(30日)
111

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

seanb4t/codegraph-go のほかの issue

seanb4t/codegraph-go の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。