-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix on save does not respect finder #179
Comments
I guess it's because the plugin has an extra setting (exclude). I think it should rather be include but why have it at all? |
I also tried to use a negated glob (ext glob is enabled by default in |
Tried it again with:
Which seems to work files outside of |
when use this extension to fix a file, it create a tmp file and then pass to php-cs-fixer, not the current edited file, maybe the config in is useless. "php-cs-fixer.pathMode": {
"type": "string",
"enum": [
"override",
"intersection"
],
"default": "override",
"description": "--path-mode can be override or intersection, intersection only works on explorer context menu action, not works for current focused file. detail see:https://github.com/FriendsOfPHP/PHP-CS-Fixer#usage"
}, and see this extension's config: pathMode, this option always
if you want the config in to work, you can use the command so i think the best way is using the option: php-cs-fixer.exclude, if you fix the current edited file. |
To the topic about the |
Why the temp file? |
because use tmp file, so the config in can't match the tmp file path generally. why i use tmp file? |
Looks like fix on save does not respect the finder object.
I've created a finder with
in('/foo/bar')
, created a file/baz.php
and it gets auto fixed on save, but it should not. This can make the plugin unusable, can someone confirm this?The text was updated successfully, but these errors were encountered: