Skip to content
This repository was archived by the owner on Sep 10, 2024. It is now read-only.
This repository was archived by the owner on Sep 10, 2024. It is now read-only.

Multiple versions of dapper collide #47

@RylanH

Description

@RylanH

If you have multiple versions of dapper in the same application (i.e. because of npm link), you have to configure one or the other to use a special classNamePrefix. It would be nice if dapper just automatically used different keys.

Options for solution:

  1. Use a truly global unique id
  2. Use a random value prefix (still could potentially collide)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions