Fix casing on case-insensitive filesystems #67
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed an issue where vscode seems to be passing a cached filename on case-insensitive file systems on file events. This PR pulls the latest filename from the system by grabbing the current casing before passing off the file path in
PintEditService.formatFile
function.Steps to reproduce:
.vscode/settings.json
pint.json
config file like so:app/Actions/wrongCasing.php
and save it with autoformatting:app/Actions/wrongCasing.php
>app/Actions/wrongCasing2.php
>app/Actions/WrongCasing.php
The file itself still has a class name of
wrongCasing
instead ofWrongCasing
derived from the filename.