- Merge request !11Issue #3324600: Incompatibility with the external_entities module → (Open) created by robertom
- last update
over 1 year ago 8 pass - last update
over 1 year ago Composer require failure - last update
over 1 year ago 8 pass - First commit to issue fork.
- last update
11 months ago 8 pass - last update
11 months ago 8 pass - Status changed to Needs work
11 months ago 6:19pm 8 December 2023 - 🇺🇸United States mglaman WI, USA
Is it possible to just widen the requirements to
^1 || ^2
instead of dropping support for^1
?Per https://github.com/Galbar/JsonPath-PHP/blob/master/CHANGELOG.md I don't see any breaking changes but it does modify some behavior. Honestly it could probably be updated to:
^1 || ^2 || ^3
. - 🇫🇮Finland kirkkala Helsinki
I am having trouble with updating my composer lockfile - I keep getting the error about
galbar/jsonpath
version. The setup has bothdrupal/next
(requires subrequests) anddrupal/external_entities
modules that requiregalbar/jsonpath
:Problem 1 - Root composer.json requires drupal/external_entities ^2.0@beta -> satisfiable by drupal/external_entities[2.0.0-beta1]. - drupal/external_entities 2.0.0-beta1 requires galbar/jsonpath ^2.0 -> found galbar/jsonpath[2.0, 2.1] but the package is fixed to 1.3.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
I do have the patch from this issue, also tried patching locally. I am now suspecting composer somehow check the dependencies before patch is applied and stops me from updating lockfile.
Would it be possible to have patched version released that allow
"galbar/jsonpath": "^2.0"
, requirement? Thanks!