WordPress / WordPress/phpdoc-parser
Bug: Extended Namespaces are preventing files from importing
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 239
- Forks
- 81
- Avg merge
- 16h 29m
- Merged PRs (30d)
- 8
Description
I'm not able to get any file that uses Namespaces extensively. A single Namespace is acceptable but longer Namespaces are ignored.
Any chance of getting this fixed or know of a workaround?
Example of a class using Namespaces that are ignored.
<?php
namespace MainNamespace\SecondName;
use \Automattic\WooCommerce\Checkout\Helpers\ReserveStock;
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the PHP namespace and use example in the report, then locate the parser entry point that handles namespaces and imports. Add a regression test for the extended namespace case and verify that the imported class is no longer ignored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100