arthurkushman /
querypath
| 1 | <?php |
||
| 2 | /** |
||
| 3 | * @file |
||
| 4 | * The main Traverser interface. |
||
| 5 | */ |
||
| 6 | |||
| 7 | namespace QueryPath\CSS; |
||
| 8 | |||
| 9 | /** |
||
| 10 | * An object capable of walking (and searching) a datastructure. |
||
| 11 | */ |
||
| 12 | interface Traverser { |
||
| 13 | /** |
||
| 14 | * Process a CSS selector and find matches. |
||
| 15 | * |
||
| 16 | * This specifies a query to be run by the Traverser. A given |
||
| 17 | * Traverser may, in practice, delay the finding until some later time |
||
| 18 | * but must return the found results when getMatches() is called. |
||
| 19 | * |
||
| 20 | * @param string $selector |
||
| 21 | * A selector. Typically this is a CSS 3 Selector. |
||
| 22 | * @return \Traverser |
||
|
0 ignored issues
–
show
|
|||
| 23 | * The Traverser that can return matches. |
||
| 24 | */ |
||
| 25 | public function find($selector); |
||
| 26 | /** |
||
| 27 | * Get the results of a find() operation. |
||
| 28 | * |
||
| 29 | * Return an array of matching items. |
||
| 30 | * |
||
| 31 | * @return array |
||
| 32 | * An array of matched values. The specific data type in the matches |
||
| 33 | * will differ depending on the data type searched, but in the core |
||
| 34 | * QueryPath implementation, this will be an array of DOMNode |
||
| 35 | * objects. |
||
| 36 | */ |
||
| 37 | public function matches(); |
||
| 38 | } |
||
| 39 |
The issue could also be caused by a filter entry in the build configuration. If the path has been excluded in your configuration, e.g.
excluded_paths: ["lib/*"], you can move it to the dependency path list as follows:For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths