You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 10, 2024. It is now read-only.
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:
Use a truly global unique id
Use a random value prefix (still could potentially collide)
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: