We could not synchronize checks via GitHub's checks API since Scrutinizer's GitHub App is not installed for this repository.
These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
2 | |||
3 | declare(strict_types=1); |
||
4 | |||
5 | namespace Overblog\GraphQLBundle\Config\Parser; |
||
6 | |||
7 | use Symfony\Component\Config\Resource\FileResource; |
||
8 | use Symfony\Component\DependencyInjection\ContainerBuilder; |
||
9 | use Symfony\Component\DependencyInjection\Exception\InvalidArgumentException; |
||
10 | use Symfony\Component\Yaml\Exception\ParseException; |
||
11 | use Symfony\Component\Yaml\Parser; |
||
12 | |||
13 | class YamlParser implements ParserInterface |
||
14 | { |
||
15 | /** @var Parser */ |
||
16 | private static $yamlParser; |
||
17 | |||
18 | /** |
||
19 | * {@inheritdoc} |
||
20 | */ |
||
21 | 30 | public static function parse(\SplFileInfo $file, ContainerBuilder $container): array |
|
22 | { |
||
23 | 30 | if (null === self::$yamlParser) { |
|
24 | 1 | self::$yamlParser = new Parser(); |
|
25 | } |
||
26 | 30 | $container->addResource(new FileResource($file->getRealPath())); |
|
27 | |||
28 | try { |
||
29 | 30 | $typesConfig = self::$yamlParser->parse(\file_get_contents($file->getPathname())); |
|
30 | 1 | } catch (ParseException $e) { |
|
0 ignored issues
–
show
|
|||
31 | 1 | throw new InvalidArgumentException(\sprintf('The file "%s" does not contain valid YAML.', $file), 0, $e); |
|
32 | } |
||
33 | |||
34 | 29 | return \is_array($typesConfig) ? $typesConfig : []; |
|
35 | } |
||
36 | } |
||
37 |
Scrutinizer analyzes your
composer.json
/composer.lock
file if available to determine the classes, and functions that are defined by your dependencies.It seems like the listed class was neither found in your dependencies, nor was it found in the analyzed files in your repository. If you are using some other form of dependency management, you might want to disable this analysis.