Styleci bridge

[soullivaneuh]

As discussed on Gitter.

cc @theofidry

[webmozart]

Thanks for this! :)

[webmozart]

What does this mean?

[soullivaneuh]

Risky fixers are not allowed by default on 2.x.

But it's possible you don't need it with your configuration. Will try and remove it if it's true.

[webmozart]

Any update on this?

[webmozart]

When I try this, I get a:

PHP Fatal error: Call to undefined method Symfony\Component\Finder\Iterator\RecursiveDirectoryIterator::isAccepted()

with php-cs-fixer 1.10.1. Is this familiar?

[soullivaneuh]

Well, never get this error.

Could you please give me the complete entered command and composer info -i result?

[soullivaneuh]

I reproduced it but I didn't find where is the issue yet.

You can avoid this error by setting prefer-stable to true on your composer.json.

[soullivaneuh]

More strange thing, the error seems to come from your code:

PHP Fatal error: Call to undefined method Symfony\Component\Finder\Iterator\RecursiveDirectoryIterator::isAccepted() in /home/sullivan/projects/fork/puli-cli/vendor/symfony/finder/Iterator/FilenameFilterIterator.php on line 30

[webmozart]

Ah, I just realized what the problem is. You are loading the project's autoloader in .php_cs, which may conflict with the libraries bundled with php-cs-fixer (and that seems to be the case right now).

[soullivaneuh]

You are loading the project's autoloader in .php_cs

Yes, this is needed to get the bridge working.

which may conflict with the libraries bundled with php-cs-fixer (and that seems to be the case right now)

Yeah, but what I don't understand is the location of the error. Regarding php trace, it seems to provide from your code. That makes no sense to me. Any idea?

[soullivaneuh]

Well, I was wrong this is coming from Symfony vendor, not your code.

But it's not an error from my lib call, this is hard to debug.

[soullivaneuh]

@webmozart Could you tell me if you still get this error with the following modification?

If it's solved, I'll try to make a custom loader on my project to prevent this kind of things.

Ref: composer/composer#1493 (comment)

[soullivaneuh]

@webmozart Should be ok this time. :-)

I released a new patch version of the bridge with a custom loader to avoid this kind of conflicts. 👍

[webmozart]

Nice, thanks :) How do you run PHP-CS-Fixer? The tool hangs for me.. there must be an infinite loop somewhere.

[webmozart]

Ah, no! Apparently it just takes a lot of network bandwidth and I'm on a slow connection right now. Why is that so?

[soullivaneuh]

it just takes a lot of network bandwidth and I'm on a slow connection right now. Why is that so?

The bridge does not download anything... Oo

What is your command?

Just run php-cs-fixer fix -v on your project root directory and you are good to go.

[soullivaneuh]

ping @webmozart

[webmozart]

Hm, seems to work now.

[soullivaneuh]

Hm, seems to work now.

I ensure you that no internet connection is done from the bridge.

If you have some, this is from another library / tools.

[webmozart]

I just reviewed your autoload.php, but I don't get how this is different now. What's the point of this custom class loader? You are still forwarding everything to the project's autoloader, no?

[soullivaneuh]

You are still forwarding everything to the project's autoloader, no?

Yes, but I only load needed classes on runtime. So, no conflict like you got.

[webmozart]

Yes, but I only load needed classes on runtime.

Can you explain this a bit more? I thought loading the classes at runtime was the purpose of Composer's autoloader?

[soullivaneuh]

I thought loading the classes at runtime was the purpose of Composer's autoloader?

I'm not an expert but I don't think so. Seems all classes are registered.

That why the unregister method of the default autoloader is called on composer/composer#1493 (comment).

[soullivaneuh]

BTW, this autoload is used only for php-cs-fixer. No side effect with your project.

[webmozart]

I'm not an expert but I don't think so. Seems all classes are registered.

Registered, yes, but not loaded. Classes are only loaded when they are used (e.g. new <Class>()), so your class loader doesn't make any difference except for calling __static() after loading a class (why?).

[soullivaneuh]

Well, you're right, I asked Seldaek for more info.

I think this is related to autoload_real.php. I think some class are loaded inside:

// autoload_real.php @generated by Composerclass ComposerAutoloaderInit065a5b652db51bcdb5d3d6134bf669ad
{
privatestatic$loader;
publicstaticfunctionloadClassLoader($class)
{
if ('Composer\Autoload\ClassLoader' === $class) {
require__DIR__ . '/ClassLoader.php';
}
}
publicstaticfunctiongetLoader()
{
if (null !== self::$loader) {
returnself::$loader;
}
spl_autoload_register(array('ComposerAutoloaderInit065a5b652db51bcdb5d3d6134bf669ad', 'loadClassLoader'), true, true);
self::$loader = $loader = new \Composer\Autoload\ClassLoader();
spl_autoload_unregister(array('ComposerAutoloaderInit065a5b652db51bcdb5d3d6134bf669ad', 'loadClassLoader'));
$map = require__DIR__ . '/autoload_namespaces.php';
foreach ($mapas$namespace => $path) {
$loader->set($namespace, $path);
}
$map = require__DIR__ . '/autoload_psr4.php';
foreach ($mapas$namespace => $path) {
$loader->setPsr4($namespace, $path);
}
$classMap = require__DIR__ . '/autoload_classmap.php';
if ($classMap) {
$loader->addClassMap($classMap);
}
$loader->register(true);
$includeFiles = require__DIR__ . '/autoload_files.php';
foreach ($includeFilesas$file) {
composerRequire065a5b652db51bcdb5d3d6134bf669ad($file);
}
return$loader;
}
}
functioncomposerRequire065a5b652db51bcdb5d3d6134bf669ad($file)
{
require$file;
}

BTW, removing the __static() still working.

[soullivaneuh]

@webmozart I asked for that. Please see composer/composer#1493 (comment).

[theofidry]

@soullivaneuh any progress?

[soullivaneuh]

@theofidry for me the PR is ready.

Waiting @webmozart confirmation since the question asked to Seldaek.

[soullivaneuh]

Hi @webmozart, going back to this old and tricky PR. :-)

I removed the custom autoload requirement.

Your issue mentioned in #21 (comment) looks to happen only when running php-cs-fixer from a global composer installation.

Tries with the .phar and with a local composer installation, working great actually.

I would just recommend to use the .phar and I think this is also the recommended way from PHP-CS-Fixer itself.

I already have strange errors like this with composer globally installed tools.

Recently with PHPUnit, telling me test passes when it should fail because I didn't require symfony/dependency-injection. Why? Simply because this dependency is globally installed and loaded too.

Ready to merge for my side. 👍