This isn't exactly an issue, but the naming mongoose-uuid2 of the node package seems confusing to me (as if it's specified only to UUID v2). mongoose-uuid seems to be already taken and maybe that's the reason for the current naming.
I'd suggest using something like mongoose-type-uuid. It's a bit verbose, but also clear to readers what's this package about.
Thanks for the makers of this package. It made it a breeze to use UUIDs as document ids.
Hi there,
This isn't exactly an issue, but the naming
mongoose-uuid2
of the node package seems confusing to me (as if it's specified only to UUID v2).mongoose-uuid
seems to be already taken and maybe that's the reason for the current naming.I'd suggest using something like
mongoose-type-uuid
. It's a bit verbose, but also clear to readers what's this package about.Thanks for the makers of this package. It made it a breeze to use UUIDs as document ids.
Good luck, Emad