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
I've found myself encoding the UUID to Base64 and Base32 string in multiple projects I worked on.
Do you think it's a good idea if we add this encoding and decoding to this library or that's out of its scope?
Thanks
The text was updated successfully, but these errors were encountered:
One use case is when I use UUIDs in URLs. Base64 produces shorter string representation. in case I need shorter case-insensitive UUID string I use Base32.
Personally, I'd argue that this would be an unnecessary extension, since it would essentially be 1-line pass-through calls to base64.UrlEncoding.EncodeToString(u.Bytes()) and base32.StdEncoding.EncodeToString(u.Bytes()).
I have a wrapper which uses base58, a handy middle ground which is used widely https://github.com/wolfeidau/shortuuid, as you say it is a pretty simple wrapper around existing UUID libraries.
Keen to migrate this to this library so i can try out v6 UUIDs.
I've found myself encoding the UUID to Base64 and Base32 string in multiple projects I worked on.
Do you think it's a good idea if we add this encoding and decoding to this library or that's out of its scope?
Thanks
The text was updated successfully, but these errors were encountered: