Laravel Pint is an opinionated PHP code style fixer for minimalists.

With php-cs-fixer it is possible to define an Indent and Line Ending besides to the rules:

	->setIndent("\t")
	->setLineEnding("\n")
	->setRules([
     //...

Dont blame me for that, but i want to have tabs instead of spaces for Indentation. Vanilla php-cs-fixer is doing that fine, but i dont see a way yet to set Indent and Line Ending in pint.json.

This MUST have the ability to set the indentation level and type if it's to be useful at all.

I, along with a great many others, don't use 4 spaces to indent. PHP-CS-Fixer has the ability to set the indentation as referenced in #24

I would suggest implementing this as a rule just as StyleCI does:

tab-width: (int)
use-tabs: (bool)

Please add this as I'm not able to use your package until you do.

Thanks

• Pint Version: 0.2.1
• PHP Version: 8.0.13 (locally installed on Windows)

Description:

I'm using WSL2 with Sail. At this point, I'm trying to use PHPStorm to automatically run Pint on the current PHP file, which works correctly when I'm on a local path.

The issue comes when you open a project from the WSL UNC path (network share). For instance, my project is located at \\WSL$\UBUNTU\home\morfra\code\XXX

Here is the full error when running the following command:

cmd.exe /D /C call C:\Users\morfra\AppData\Roaming\Composer\vendor\bin\pint.bat \\wsl$\Ubuntu\home\morfra\code\XXX\app\Http\Middleware\RecordPageViewsToActivityLog.php
'\\wsl$\Ubuntu\home\morfra\code\XXX'

In Runner.php line 242:
                                                                                                                       
  Cannot write to file "\\WSL$\UBUNTU\home\morfra\code\refonte-intranet\app\Http\Middleware\RecordPageViewsToActivity  
  Log.php" as it is not writable.

That being said, Windows specifically says "UNC paths are not supported in CMD", but I've never had any issues with other scripts running like that.

Steps To Reproduce:

Run the pint.bat command from Windows against a UNC path: pint.bat "\\wsl$\Ubuntu\home\morfra\code\XXX\app\Http\Middleware\RecordPageViewsToActivityLog.php"

• Pint Version: 0.1.5
• PHP Version: 8.0.20

Description:

I've tried this in two local Lara projects. Running ./vendor/bin/pint results in an error shown below

Steps To Reproduce:

composer require laravel/pint --dev

then

./vendor/bin/pint

Am I missing something?

• Pint Version: 1.2.1
• PHP Version: 8.1.12

Description:

We have developers who use windows in local environment, so we have core.autocrlf=true in git to preserve the CRLF on windows but commit with LF.

When running pint, it changes all the line endings from CRLF to LF causing hundreds of changed files in the source control, even when the content wasn't changed at all.

I think the expected behaviors would be to preserve the line endings of the target OS. Or do you recomend us to switch to disable core.autocrlf?

Steps To Reproduce:

1. Enable core.autocrlf=true if not already enabled: git config --global core.autocrlf true
2. Clone any laravel repository and composer install.
3. Run Laravel pint.

All the CRLF will be changed to LF causing hundreds of file changes.

Could there be two sentences about why to use Pint over PHP-CS-Fixer?

I imagine the output might be more enjoyable and I imagine the installation being easier.

Is that correct? But likely pint could get old as it comes bundled with a PHP-CS-Fixer, right?

👋 there, congrats for the release @nunomaduro

Many code quality tools provide a phar version ( PHP-CS-Fixer, PHPMD, PHPStand, etc...) Will pint also provide a .phar file for each release ?

Also what about having a laravel/pint-github-action, similar to https://github.com/OskarStark/php-cs-fixer-ga

• Pint Version: 0.2.4
• PHP Version: 8.1.8

Description:

Previous versions of pint worked with the following configuration, correctly placing braces where they should be (K&R Style)

{
    "preset": "laravel",
    "rules": {
        "simplified_null_return": true,
        "braces": {
            "position_after_functions_and_oop_constructs": "same"
        },
        "new_with_braces": {
            "anonymous_class": false,
            "named_class": false
        }
    }
}

But new pint doesn't respect this position_after_functions_and_oop_constructs value and always formats using Allman style, placing brace on the next line (which is same as "position_after_functions_and_oop_constructs": "next"

Steps To Reproduce:

Edit your pint.json file in the root directory and add the following content, and then run ./vendor/bin/pint

{
    "preset": "laravel",
    "rules": {
        "simplified_null_return": true,
        "braces": {
            "position_after_functions_and_oop_constructs": "same"
        },
        "new_with_braces": {
            "anonymous_class": false,
            "named_class": false
        }
    }
}

Hi,

I have a GitHub Org that has many Laravel apps. We currently have our own private coding standards repository which applies the same PHP CS Fixer rules across the organisation.

Is this same thing possible with Pint? We'd love to switch this over to use Pint but we don't really want to have to replicate the ruleset across all the applications, we'd rather this existed in a one centralised place across the whole organisation.

Cheers.

• Pint Version: 0.1.5
• PHP Version: 8.1.1

Description:

Enum cases should not be reformatted even regardless of keyword name.

Enum class: app/Enum/SegmentCastMissingAs.php

namespace App\Enum;

enum SegmentCastMissingAs: string
{
    case NULL = 'null';
    case FALSE = 'false';
    case TRUE = 'true';
    case EMPTY_STRING = 'empty_string';
    case ZERO = 'zero';
    case IGNORE = 'ignore';
}

Pint change this style using Laravel preset:

-case NULL = 'null';
-case FALSE = 'false';
-case TRUE = 'true';
+case null = 'null';
+case false = 'false';
+case true = 'true';
case EMPTY_STRING = 'empty_string';
case ZERO = 'zero';
case IGNORE = 'ignore';

Steps To Reproduce:

1. create class app/Enum/SegmentCastMissingAs.php
2. Run /vendor/bin/pint --preset laravel app/Enum/SegmentCastMissingAs.php

I believe it is an important feature to allow for passing list of files which should be formatted upon run instead of formatting all files. This is usable in case formatting is happening on pre-commit hook (for example in our case we have lint-staged configured which is formatting staged PHP files before commit). I don't see this anywhere as a documented feature and the command input arguments also does not seem to allow for this.

This pull request should ideally target an new version of Laravel Pint, that should ship by default in Laravel 10.x. Please check https://github.com/laravel/laravel/pull/6010 for details about this pull request.