Default namer not fully implemented

Open LouTerrailloune opened this issue 12 years ago • 2 comments

If you don't put namer: ~ in your mapping configuration, conflicting files are not renamed (and I think they should, using the default namer).

Oct 24 '13 07:10 LouTerrailloune

In fact I think the documentation is wrong when stating that the default namer is used when none is specified in config, because if you don't define a namer, none is used and the filename is not changed at all.

Oct 24 '13 08:10 LouTerrailloune

How do we solve this issue ? fix the documentation or use the default namer if none is specified (no 'namer' entry in config) I can make a PR

Aug 07 '15 18:08 LouTerrailloune