Skip to content
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

allow "spotlessFiles" project property in gradle plugin to only target specific files #322

Merged
merged 6 commits into from
Dec 13, 2018
Merged

Conversation

vmdominguez
Copy link
Contributor

Added a -files switch to allow targeting specific files.

This can be part of a solution to #178, the first part being a script that uses git commands to retrieve a list of staged files.

- update change log to reflect namespaced property
- remove superfluous assert statement
- compile Patterns once
Copy link
Member

@nedtwigg nedtwigg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR! Looks great except for a very subtle bug that's pretty easy to fix.

@vmdominguez vmdominguez changed the title allow "files" project property in gradle plugin to only target specific files allow "spotlessFiles" project property in gradle plugin to only target specific files Dec 12, 2018
@nedtwigg
Copy link
Member

This LGTM. I'll cut a release tomorrow unless somebody has more comments or another PR they'd like to get merged in.

@nedtwigg nedtwigg merged commit 249d3ca into diffplug:master Dec 13, 2018
@nedtwigg
Copy link
Member

Published as 3.17.0

@luis-fors-cb luis-fors-cb mentioned this pull request Apr 11, 2019
@shaka-b
Copy link

shaka-b commented May 16, 2019

Have you test the file pattern on window? On my windows machine the pattern matching used here always fails when using UNIX path seperator "/" as described in the README.

@nedtwigg
Copy link
Member

Might be worth creating a fresh issue for this.

@nedtwigg
Copy link
Member

nedtwigg commented Jun 5, 2020

FYI, -PspotlessFiles has been deprecated and will be removed. Migration path available here: #602

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants