-
I'd like to use your pagination via composer. Is it possible to make your package psr compatible and add a composer.json in it?
-
I think it would benefit the project in case the code base followed the [PSR-2](http://www.php-fig.org/psr/psr-2/) coding style standards. Currently e.g. the following rules are violated:
- _Code M…
-
It is our intention to follow psr-12 `Extended Coding Style Guide` (https://github.com/php-fig/fig-standards/blob/master/proposed/extended-coding-style-guide.md) if/when it passes. Even if it contradi…
-
-
As @wilson1000-MoJ suggested in this review. https://github.com/ministryofjustice/justice-gov-uk/pull/77#discussion_r1512622834
It's important to use a standard for code readability, and minimise …
-
In order to avoid any potential conflicts with other plugins, it's better to use namespaced classes. An added perk is using PSR-12 autoloading. Even if WordPress is not implementing PSR-12 autoloading…
-
Are there any plans for PSR-7 support? It would be great if we could set up tracking and then get a PSR-7 request from the tracker to send it out using our own HTTP client. Also creating a new tracker…
-
Hey Folks!
We just pulled this project into a site we're working on and realized that none of the code is namespaced per PSR-4 conventions which makes it a little unconventional to work with. Would…
-
Right now, this package uses `Captcha` as its only namespace, which is a bit unfortunate, since it is a very generic namespace which increases the risk of collisions when used e.g. in an environment w…
flack updated
9 years ago
-
Viabill module is not compatible with magento 2.4.7 and php 8.2
- Root composer.json requires magento/product-community-edition 2.4.7 -> satisfiable by magento/product-community-edition[2.4.7].
…