Closed sonicpunk closed 3 years ago
Oh yeah Composer 2.1.3
So that happens on a clean (no packages or content) MODX3 install?
That is an install with some modx extras as well. So not clean.
I seem to have found the issue. We have a module using Yaml 4, which conflicts with Gitify because it is expecting Yaml version 2 and Gitify is directly calling a method in Yaml 2. If I deinstall this module, Gitify works again.
I wonder how MODX is going to handle this autoloading issue. This issue I see will be coming up again and again when other developers start developing extras with their own PHP library dependencies that could cause conflicts with other extras.
There's not really s solution for that, as long as each extra can define their own dependencies there'll occasionally be conflicts.
I'd very much welcome the help bringing gitify up to date, it's quite a bit behind.
Should be resolved by updating to v2; see the readme for instructions.
Summary
This may be a general issue with MODX3 as we are moving to a composer based setup, but... I am getting this error when trying to run Gitify:
Step to reproduce
We have an environment whereby Gitify is already installed for our projects. A docker image. Fitting MODX3 to this environment required us to run composer install within our MODX folder. After this, I attempted to run a Gitify extract command.
Observed behavior
If resulted in the error above.
Expected behavior
Would love it to work.
Environment
Gitify version 0.12.0, MODX version 3, Operating System Apache, MySQL version 5.6, PHP version 7.3, etc.