-
For discussion - should we be adopting PSR-2 coding style for Indicia: https://en.wikipedia.org/wiki/PHP_Standard_Recommendation?
Although not adopted by the Drupal community it is widely used for…
-
Can we change coding standards to be PSR-2 compatible?
-
As title, I think we can follow the `PSR-2` coding style for `src` and `test` folder.
-
### Is your feature request related to a problem?
Using OpenSearch client in combination with New Relic (e.g. when migrating from Elasticsearch)
does not work immediately. I.e. OpenSearch client doe…
-
http://www.php-fig.org/psr/psr-2/
Note that PSR-2 requires compliance with PSR-1, which in turns states that _Namespaces and classes MUST follow an "autoloading" PSR_. Consequently, we'll also adopt …
-
After upgrading "[psr/http-message](https://www.php-fig.org/psr/psr-7/)" from version 1.1 to 2.0 this bundle can't be used anymore and you get the following error log:
```
php.CRITICAL: Fatal Comp…
-
```
We should use the accepted standard rather than doing our own thing.
* https://github.com/php-fig/fig-standards/tree/master/accepted
```
Original issue reported on code.google.com by `jukka.m.sv…
-
**Describe the bug**
Composer is yelling about a variety of classes not conforming to PSR-4 autoloading standards:
```
Class ActionScheduler_AsyncRequest_QueueRunner located in ./web/app/plugins/…
-
- Deployer version: 7.3.3
We are using the AWS SDK within our `deploy.php` file to fetch some data that we need for our deployments. However, since upgrading to more recent versions of the AWS SDK …
-
I published the language files and changed filament-settings-hub::messages.group to "Administration", but the change was not reflected on the navigation menu. "Settings" continues to appear on the men…