This is the message output,

in config a use extensions: vendor/bin/pint

i tried with this path on windows: ./vendor/bin/pint vendor/bin/pint.bat

not working in windows.

In linux only i use vendor/bin/pint

update:

if i use tha absolute from C....\laravel-project\vendor\bin\pint.bat

then its works

Originally posted by @jesusferm in https://github.com/open-southeners/vscode-laravel-pint/issues/15#issuecomment-1192841549

Issue

I believe there might be some issues with formatting on markdown email blade files. Which according to the docs explain to not add excess indentation.

To recreate this issue you can build an example Mail with the example from Laravel

php artisan make:mail OrderShipped --markdown=emails.orders.shipped

Which should give you a blade file like so:

@component('mail::message')
# Order Shipped
 
Your order has been shipped!
 
@component('mail::button', ['url' => $url])
View Order
@endcomponent
 
Thanks,<br>
{{ config('app.name') }}
@endcomponent

Now I have the following VSCode settings:

{
    "editor.formatOnSave": true,
    "[vue]": {
        "editor.defaultFormatter": "esbenp.prettier-vscode"
    },
    "[javascript]": {
        "editor.defaultFormatter": "esbenp.prettier-vscode"
    },
    "[typescript]": {
        "editor.defaultFormatter": "esbenp.prettier-vscode"
    },
    "[php]": {
        "editor.defaultFormatter": "open-southeners.laravel-pint",
        "editor.formatOnSave": true
    }
}

So when I save that file is gets formatted as so

@component('mail::message')
    # Introduction

    The body of your message.

    @component('mail::button', ['url' => ''])
        Button Text
    @endcomponent

    Thanks,<br>
    {{ config('app.name') }}
@endcomponent

Which causes the email to look a little like

Current Workaround

Right now my workaround is to add back my previous formatter, or turn off complelty for those blade type files

    "[blade]": {
        "editor.defaultFormatter": "valeryanm.vscode-phpsab",
        "editor.formatOnSave": true
    },

First off thank you for creating this, much better setup than i had before.

That being said, my recommendation is to keep the out of the box experience with this plugin as a "run pint".

It took me a few mins to realize that the plugin was actually working, it was just using the --preset psr12 flag

Plus chances are, if a user does have opinions on what they want to use they will likely already be using pint.json

I'm getting this message "Something went wrong! Executable does not exists or lacks permissions." I have the pint.json on the project root and when I run ./vendor/bin/pint its works.

What might be the problem?

After upgrading to v0.7.2 of this extension, I get the error "Something went wrong! Executable does not exists or lacks permissions." for manual or automatic formatting on save. Downgrading the plugin back to v0.7.1 solves this problem, without any additional modifications to the settings or the executable.

The executable is on it's default location (./vendor/bin/pint) and the permissions are looking okay.

Running with Pint v0.2.3.

The following error is thrown on every save of every file for projects that don't have Pint installed. This is a bit annoying and counterintuitive. I feel that no warning should be thrown here.

Something went wrong! Executable does not exists or lacks permissions.

It's returning this message when I'm working in a vscode workspace.

I tried to reproduce the problem by opening in a regular window and it didn't happen, I noticed this only for the workspace.

When I use VSCode Command it is working fine, this was only noticed for format on save

My development environment is macOS and I use php by command line via asdf

Hi,

I've tried using your extension and couldn't get it to work in my current project. I'm not sure if it's relevant but my Laravel application code is stored in a code directory at the root of the project like so:

| azure
| code
   | app
   | bootstrap
   | config
   | ...
| docker

When I tried it on a brand new Laravel project it worked.

Also, I tried changing the configuration for the executable path to "./code/vendor/bin/pint" with no effect.

I'm trying v0.2.1 and the install gets stuck when I try to install it in WSL2 (Ubuntu + W11). So basically can't use it cause it's disabled in workspace unless I manage to install it in remote WSL

I have a variety of project types I work with and this extension seems to automatically modify the workspace's .vscode/settings.json file. It's adding this line specifically:

"laravel-pint.enable": true

It would be nice to either:

1. Remove this functionality
2. Hide it behind a config option and set it in my user settings to not offer to modify my workspace settings every time I open a project.

The config file setting is not being passed to the pint command correctly. It appears to be using just the filename, instead of either the relative or absolute path of the config file. My laravel project is inside an api/ folder in the workspace. Additionally, it seems like allowing any of the following paths should be acceptable:

• /project/api/pint.json
• api/pint.json -./api/pint.json

It seems like the extensions should resolve the absolute command based on any of the above inputs and pass the absolute path of the file like the rest of the args.

.vscode/settings.json

{
  "editor.formatOnSave": true,
  "laravel-pint.enable": true,
  "laravel-pint.enableDebugLogs": true,
  "laravel-pint.configPath": "api/pint.json",
  "[php]": {
    "editor.defaultFormatter": "open-southeners.laravel-pint"
  }
}

api/pint.json

{
    "preset": "laravel",
    "rules": {
        "braces": true,
        "not_operator_with_successor_space": false,
        "ordered_imports": {
            "sort_algorithm": "length"
        },
        "concat_space": {
            "spacing": "one"
        }
    }
}

Output:

"/project/api/vendor/bin/pint --config pint.json /project/api/tests/Feature/File.php"
["INFO" - 6:21:57 PM] Formatting completed in 899ms.

When falling back to the global pint command, I realized that the workspace config isn't being used.

I haven't tested all the use cases thoroughly yet, so leaving this as a draft for the moment.

Describe the bug Got this error in the console (wasn't there before): ["INFO" - 7:36:37 a.m.] Extension Name: open-southeners.laravel-pint. ["INFO" - 7:36:37 a.m.] Extension Version: 1.1.4. ["ERROR" - 7:36:52 a.m.] Executable not readable or lacks permissions for Laravel Pint.

Environment:

• Operating system: Linux
• IDE / version: VSCode 1.73.1
• Extension version 1.1.4
• Extension's config:

{
 "laravel-pint.executablePath": "./code/vendor/bin/pint",
 "laravel-pint.preset": "psr12",
 "laravel-pint.configPath": "./code/pint.json"
}