You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When parsing code that contains hierarchical namespaces, e.g.,
namespaceMy\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.
The text was updated successfully, but these errors were encountered:
When parsing code that contains hierarchical namespaces, e.g.,
terms are created for each step in the hierarchy (
My
,Hierarchical
andNamespace
in the example above), but since cache invalidation is suspended during a parse, thewp-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 backendWP_Parser\Importer::import()
correctly deleteswp-parser-package_children
andwp-parser-since_children
at the end of the parse (which will result in them being rebuilt at the appropriate time), but it seems thatwp-parser-namespace_children
was forgotten.PR coming shortly.
The text was updated successfully, but these errors were encountered: