v1.2.0

Added

• Pint --dirty option as a extension setting [#60] (thanks @tobinguyenn)

v1.1.8

Fixed

• Windows paths [#55 #57] (regression from d421f4b, thanks @balthild)

Changed

• Pint config json schema updated to PHP CS Fixer 3.49.0

v1.1.6

Fixed

• Use relative path as Pint uses current working directory (cwd) [#50 #51] (thanks @mho22)
• Ignore VSCode excluded paths so Pint executable can be found [#46 #45] (thanks @fritz-c)

Changed

• VSCode minimum version upgraded (1.68.0 to 1.82.0)
• Pint config json schema updated to PHP CS Fixer 3.41.1

v1.1.5

Added

• PER preset to JSON schema and config [#41]
• Fixes to JSON schema generator [#40 #42] (thanks @yaegassy)

v1.1.4

Fixed

• Issue resolving fallback to global Pint binary [#28] (thanks @jasonvarga)

v1.1.3

Added

• Extension published to Open VSX for VSCodium users: https://open-vsx.org/extension/open-southeners/laravel-pint

v1.1.2

Changed

• Use global context for extension initial installation auto-config [#24]

v1.1.1

Fixed

• Custom config file path resolution (now yes, thanks to @adrum for the PR) [#23]
• Workspace files format command

Changed

• laravel-pint.configPath now is also being used by the extension's exclude paths

v1.1.0

Added

• More logging debug information (only enabled by setting the option laravel-pint.enableDebugLogs)

Changed

• Format workspace was formatting all workspaces, now it formats only current active document's workspace (otherwise it complains about it on the Output logs tab of VS Code)

Fixed

• Custom config file path resolution [#22]
• File formatting triggers under the whole workspace [#21]
• Minor bug with extension version debug info getting logged

v1.0.2

Fixed

• Order of command arguments on PHP when running in Windows (thanks @serdartaylan) [#18]