-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
ext: '' should remove the extension #1087
Comments
That was lightning fast, thank you. |
Issue submitters: don't let the fact that I closed this issue in 18 minutes go to your heads, I just happened to be working on adding the |
This does sort of introduce a weird breaking change for folks who have followed documentation that states when using the |
Just to point out what I'm talking about: files: [{
expand: true,
cwd: 'app',
src: '**',
dest: 'dist',
ext: ''
rename: function (dest, src) { console.log(src) }
}] In this case, if I have a file in |
Sorry for overcommenting, just digging through and it looks like this is actually expected functionality, as shown here and in #979. So, my question is, without digging into the source of each contributed plugin, is there a way to change extDot? Sorry if I'm just missing something totally obvious. Edit: Yes, totally missing something obvious! Maybe I should actually read the issue when I link to it: files: [{
expand: true,
cwd: 'app',
src: '**',
dest: 'dist',
ext: ''
extDot: 'last',
rename: function (dest, src) { console.log(src) }
}] Sorry @cowboy for the stream of consciousness comments. Appreciate the fix! I added it to the doc repo in gruntjs/grunt-docs#50, just so anyone else who comes across it can spend less time rambling in PR comments. |
I think that would make more sense than just ignoring the empty string and leaving the extension.
The text was updated successfully, but these errors were encountered: