value of 'wp-parser-namespace_children' option incorrect after parsing source with hierarchical nmespaces
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- php
- Domain
- documentation
Research direction
Start in WP_Parser\Importer::import(), where the parser already removes the wp-parser-package_children and wp-parser-since_children options after parsing. Confirm that hierarchical namespace terms leave wp-parser-namespace_children stale, then ensure it is invalidated at the same point. Verify that all namespace levels appear in the WP_Terms_List_Table after parsing.
Written by the indexing model from the issue text.
Description
When parsing code that contains hierarchical namespaces, e.g.,
namespace My\Hierarchical\Namespace;
class MyClass {
...
}
terms are created for each step in the hierarchy (My, Hierarchical and Namespace in the example above), but since cache invalidation is suspended during a parse, the wp-parser-namespace_children option is never updated.
This results in, among other things, only the top-level namespace term showing in the WP_Terms_List_Table in the backend
WP_Parser\Importer::import() correctly deletes wp-parser-package_children and wp-parser-since_children at the end of the parse (which will result in them being rebuilt at the appropriate time), but it seems that wp-parser-namespace_children was forgotten.
PR coming shortly.
- Dominant language
- PHP
- Stars
- 239
- Forks
- 81
- Avg merge
- 16h 29m
- Merged PRs (30d)
- 8
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.
More from WordPress/phpdoc-parser
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
WordPress/phpdoc-parser#269 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
WordPress/phpdoc-parser#268 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
WordPress/phpdoc-parser#254 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
WordPress/phpdoc-parser#246 · 9 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
WordPress/phpdoc-parser#235 · 1 comment ·
All issues in WordPress/phpdoc-parser
Similar issues
-
tooling
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
UX
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ProfessionalWiki/NeoWiki#1525 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
OpenConext/OpenConext-engineblock#2122 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Automattic/safe-publish#594 ·