PHP extractor misses PHP 8.5 void casts and match arms

[joshbruce]

Summary

The PHP AST extractor still emits partial-extraction warnings for valid PHP 8.5 syntax. In a PHP 8.5 application, Graphify 0.9.80 with tree-sitter-php 0.24.1 reports no symbols for seven files containing (void) SomeClass::someMethod(...), and a multiline parse error for a return (string) match (...) { EnumCase => ... } expression. The same repository produced ten warning candidates on Graphify 0.9.57; 0.9.80 reduces that to eight but does not cover these constructs.

Minimal syntax examples:

<?php
(void) SomeClass::someMethod($argument);

return (string) match ($mode) {
    SomeEnum::First => $object->first(),
    SomeEnum::Second => $object->second(),
};

PHP 8.5 accepts these forms. The current grammar reports an ERROR on the class name after (void) and fails to parse enum-qualified match arms in this return/cast context, which prevents useful file-level symbols from being extracted.

Expected behavior

The PHP extractor should parse these valid PHP 8.5 constructs and retain surrounding declarations, calls, and relationships. Please add parser regression tests for the snippets above; merely suppressing warnings would hide missing graph coverage.

Environment

• PHP 8.5.2
• Graphify 0.9.80 (also compared against 0.9.57)
• tree-sitter-php 0.24.1

Repository evidence is from 8fold/site-mastering-the-mundane.apps issue #217. No application source was changed to work around the parser limitation.

[github-actions]

Thanks for opening this issue, @joshbruce. A maintainer will take a look soon.

If you would like to discuss it in real time, come say hi on our Discord server. For longer-form questions and ideas there is also GitHub Discussions.

To help us triage, please make sure the report includes what you expected, what actually happened, and the steps (and a small sample) to reproduce it.

[joshbruce]

Follow-up after checking the full extractor results: Graphify 0.9.80 still reports parse errors for two additional (void)-using files, but retains limited symbols and relationships there, so they fall below the CLI's warning threshold. The eight warning files are seven files with no symbols and the match-expression file; these two partial-extraction files remain affected even though they no longer appear in that warning list. This distinction is important: fewer warnings does not mean those two files now parse completely.