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
Currently, use UUIDv4 to generate unique identifiers for our system. While UUIDv4 is a good approach to generate unique IDs, it is complete overkill. Not critical but should default to a ms timestamp-based approach for generating unique identifiers. By using timestamps, we can generate unique IDs that are ordered by time, and there won’t be collisions when run on a users local system. Should be implemented as timestamp being a default behavior and UUID as an override if collisions are an issue.
The text was updated successfully, but these errors were encountered:
Issue Description
Currently, use UUIDv4 to generate unique identifiers for our system. While UUIDv4 is a good approach to generate unique IDs, it is complete overkill. Not critical but should default to a ms timestamp-based approach for generating unique identifiers. By using timestamps, we can generate unique IDs that are ordered by time, and there won’t be collisions when run on a users local system. Should be implemented as timestamp being a default behavior and UUID as an override if collisions are an issue.
The text was updated successfully, but these errors were encountered: