-
Is there any chance the requirement for `pimple/pimple` could be increased? We are using `deployer/deployer` for our projects as a dev dependency. However, since `deployer/deployer` requires `pimple/p…
-
Does this not work with Pimple 3 and above?
ghost updated
5 years ago
-
Would you be open to changing the API to match v2 of Pimple?
For example, in v2, services are shared by default, so there's no need to call "share". Factory services can be registered via `container…
-
Thanks for this handy package. Pimple development has ended/is in maintenance mode, and I don't necessarily think this package need be aware of the dependency injection container per se. Open to decou…
-
`composer require cedaro/satispress:1.0.3` results in the following:
> Problem 1
- Root composer.json requires cedaro/satispress 1.0.3 -> satisfiable by cedaro/satispress[v1.0.3].
- cedar…
-
It looks like the composer.json needs to be updated to support the current versions of pimple being pushed out:
- Installation request for cnam/security-jwt-service-provider ^2.1 -> satisfiable by…
-
Check the link for PHP warnings on PHP 8.1
[Deprecated warnings on plugintests.com ](https://plugintests.com/plugins/wporg/greenerwp/latest)
+ on PHP 8.2 Creation of dynamic property warnings
…
-
Deprecated: Return type of Pimple\Container::offsetExists($id) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used…
-
Hi, some deprecated warnings in version 5.5.15
1×
PHP Deprecated: Return type of Pimple\Container::offsetExists($id) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool,…
-
Hi there,
first of all: Awesome plugin, solved so many headaches for me. Many thanks for developing and maintaining 🚀.
I ran into an issue when SatisPress (supposedly) updated to `1.0.3` – at le…