tree-sitter-phpdoc
tree-sitter-phpdoc copied to clipboard
PHPDoc grammar for tree-sitter
Is it possible to add support for docblock annotations? For example: ```
Add support for a special format for list arrays * Array shapes: https://psalm.dev/docs/annotating_code/type_syntax/array_types/#array-shapes * List shapes: https://psalm.dev/docs/annotating_code/type_syntax/array_types/#list-shapes ```php
Hello, I'm on neovim using treesitter and I'm encountering the following issue :  As you can see, the Variadic param type is not correctly recognized. It's considered as `@spell`...
This grammar is currently using the [`tree-sitter-php`](/tree-sitter/tree-sitter-php) grammar to do some of the "heavy lifting" for parsing language constructs that are common between PHP and phpDoc. @mikehaertl raised questions about...
#4 was a clean, expedient fix for the common problem in #3, but it introduced a known issue: any line of non-tag text, or any "description" following a tag, that...
The following items are known incomplete. They are recognized as tags, but the fields, types, optional fields, etc are not correct. - [ ] `@subpackage` - [ ] `@example` -...
Noticed while using Zed w/ this docblock: ```php /** * @method getSelectorContents(string $selector) * @method getSelectorAttribute(string $selector, string $attribute) * @method getTrimmedString(string $string) */ ``` phpstan does fine with this,...
Let's look at the example below (in Neovim): ```php /** * @param array $example */ ```  Maybe it's similar to #26.
I can't seem to get this parser to work with Rust Tree-sitter or Swift Tree-sitter. When attempting to compile the project after adding `tree-sitter-phpdoc` as a dependency I run into...
Hi there, When adding grammars, folks use specific commits to point to. Usually the commit of a release. ```toml id = "php" name = "PHP" description = "PHP support." version...