PHPackages                             apsg/coding-standards - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. apsg/coding-standards

ActiveLibrary[Utility & Helpers](/categories/utility)

apsg/coding-standards
=====================

Coding standardsfor PINT

0361

Since Mar 6Pushed 3y ago1 watchersCompare

[ Source](https://github.com/apsg/coding-standards)[ Packagist](https://packagist.org/packages/apsg/coding-standards)[ RSS](/packages/apsg-coding-standards/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependenciesVersions (1)Used By (0)

Coding standards
================

[](#coding-standards)

Usage
-----

[](#usage)

We can pass the path of the config file to Pint:

so after this package is installed:

```
composer require apsg/coding-standards
```

one can tell Pint to use this config:

```
./vendor/bin/pint --config vendor/apsg/coding-standards/pint.json
```

Alternatively - one can just copy the `pint.json` file and use it as a template in it's own projects.

Rules descriptions:
-------------------

[](#rules-descriptions)

### Namespace

[](#namespace)

```
"single_blank_line_before_namespace": false,
"no_blank_lines_before_namespace": true,
"blank_line_after_opening_tag": false,
```

Those three ( [1](https://mlocati.github.io/php-cs-fixer-configurator/#version:3.14%7Cfixer:single_blank_line_before_namespace), [2](https://mlocati.github.io/php-cs-fixer-configurator/#version:3.14%7Cfixer:no_blank_lines_before_namespace), [3](https://mlocati.github.io/php-cs-fixer-configurator/#version:3.14%7Cfixer:blank_line_after_opening_tag)) remove extra line before namespace. We don't look at this part of the file anyway, so this extra line is surplus in my opinion.

Before

```