Guzzle coflicts

  • I’m hitting conflicts between this plugin, which I’m really keen to use, and my own plugin over the use of Guzzle. I’m using a later version of Guzzle and I think the problem is to do with autoloading. One of the problems is the loading of different versions of the functions_include.php files, but I think I can work around that. The other may be related to the incomplete use of PHPScoper. In the documentation for PHPScoper it says: “PHP-Scoper does not support prefixing the dumped Composer autoloader and autoloading files. This is why you have to manually dump the autoloader again after prefixing an application.” This second dump doesn’t seem to have been done as the autoload files still have the unprefixed names in. Is there any chance that in the next release of this plugin, you could do this additional step please?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Marek Dědi?

    (@marekdedic)

    Hi,
    it’s a bit more complicated than it seems ??

    PHPScoper is indeed limited in what it can do, however, we do some post-processing of its results to mitigate that.

    See here for post-processing of both Guzzle as well as the autoload files directly in PHPScoper. And also here for additional processing of the autoload files outside of PHPScoper.

    My aim is to have everything composer-related inside the Sgdg\Vendor namespace – but if your plugin doesn’t do the same thing, than there may be some conflicts despite this. I think I don’t leak/expose anything outside this namespace, but if you do find anything, please report it and I’ll try to fix it.

    Aside: If you’d prefer, feel free to use GitHub issues for this as this is a fairly technical topic, rather than a suppport question ??

    Thanks,
    Marek

    Thread Starter peter8nss

    (@peter8nss)

    Thanks for the prompt response. Conversation moved to GitHub as suggested.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Guzzle coflicts’ is closed to new replies.