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

Multiple versions of dapper collide #47

Open
RylanH opened this issue May 5, 2017 · 3 comments
Open

Multiple versions of dapper collide #47

RylanH opened this issue May 5, 2017 · 3 comments

Comments

@RylanH
Copy link
Contributor

RylanH commented May 5, 2017

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)
@nevir
Copy link
Contributor

nevir commented May 5, 2017

Take a look at https://github.com/convoyinc/unique-type

@RylanH
Copy link
Contributor Author

RylanH commented May 5, 2017

Looks like a good match to me

@nevir
Copy link
Contributor

nevir commented May 5, 2017

It might need some love to insert separators other than :, though

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

No branches or pull requests

2 participants