Skip to content

Default namer not fully implemented #9

Open
Open
Default namer not fully implemented#9

Description

@LouTerrailloune
LouTerrailloune
opened on Oct 24, 2013

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

Activity

  1. LouTerrailloune commented on Oct 24, 2013

    @LouTerrailloune
    LouTerrailloune
    on Oct 24, 2013
    Author

    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.

  2. LouTerrailloune commented on Aug 7, 2015

    @LouTerrailloune
    LouTerrailloune
    on Aug 7, 2015
    Author

    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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions