Replies: 3 comments 2 replies
-
Why not just get |
Beta Was this translation helpful? Give feedback.
1 reply
-
Sigh... I'm not a huge fan of adding this complexity, especially for BC support. Will GraphQLite even be able to handle both of these container implementations? I haven't looked into how containers are being called within GraphQLite and what the reliance is. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Okay, feel free to submit a PR on it. Let's stick with a locked version in composer, please. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I'm stuck with the version 6.0 due to my DI container
laminas/laminas-servicemanager
, it only supportpsr/container:^1.0
.My idea is to create a sub package of
thecodingmachine/graphqlite
namedthecodingmachine/graphqlite-container
and move the namespaceTheCodingMachine\GraphQLite\Containers
in it, implementation ofpsr/container:^1.0
tagged as 1.x andpsr/container:^2.0
tagged as 2.x.This way composer will resolve the good container implementation itself.
WDYT ?
Thanks !
Beta Was this translation helpful? Give feedback.
All reactions