function "spans" #718

Activity

1. matigumma

   added

   enhancementNew feature or requestNew feature or request

   on Jun 30, 2026
2. DeusData

   added

   parsing/qualityGraph extraction bugs, false positives, missing edgesGraph extraction bugs, false positives, missing edges

   priority/backlogValuable contribution, lower scheduling urgency; review when maintainer capacity opens.Valuable contribution, lower scheduling urgency; review when maintainer capacity opens.

   on Jun 30, 2026
3. DeusData commented on Jun 30, 2026

   

   DeusData

   on Jun 30, 2026

   Owner

   More actions

   Thanks. I’m linking this into the parsing/language coverage epic, and it likely belongs with the broader VB6 handling in #721. The behavior we want is full body spans for procedures/methods, not declaration-only nodes; that should be captured by a VB fixture before implementation.
4. DeusData

   added this to the 0.9.2-rc milestone on Jul 8, 2026
5. DeusData commented on Oct 10, 2026

   

   DeusData

   on Oct 10, 2026

   Owner

   More actions

   Thanks for reporting this, and for your patience. Full procedure/method spans remain the intended behavior.

   I checked current main at 76a2485 and the v0.11.0 source. Both skip recognizable VB6 .cls and .frm exports as unsupported; that guard does not implement full VB6 body spans. Generic function/method extraction uses the selected syntax node's boundaries, so these source findings do not establish how the reported declaration-only nodes were produced or demonstrate a runtime fix.

   To clarify that specific observation, a small sanitized example would help:

   • Preserve the actual filename extension and header/prologue, include one complete procedure, and identify an interior line that should match it.
   • Include the CBM version that produced the index, the exact lookup/tool arguments, and one returned node record showing its path, name, start_line and end_line.

   One representative procedure is enough. This would help reproduce the original observation; the accepted language-coverage work remains on the maintainer side, and the issue stays open.
6. DeusData commented on Oct 19, 2026

   

   DeusData

   on Oct 19, 2026

   Owner

   More actions

   Thank you again for the procedure-span report. Checking back on the October request: one sanitized procedure, its actual extension/header, and the returned line range would clarify the declaration-only observation. Full VB6 coverage remains maintainer work under #721; this follow-up does not shift that work to you.
7. DeusData commented on Oct 25, 2026

   

   DeusData

   on Oct 25, 2026

   Owner

   More actions

   Thank you again for the report and your patience. A sanitized single procedure with its actual extension/header and returned line range remains enough for the declaration-only observation.