UUIDs #359
jerryjappinen
started this conversation in
Feature request
UUIDs
#359
Replies: 1 comment
-
@jerryjappinen that's a really useful feature not hard to implement indeed |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It's useful to have globally unique identifiers for objects in the database and exposed in the API, but from the looks of it this is currently not supported.
UUIDs also make frontend code easier to manage. For example, when you get the most up-to-date version of an object (or partial object) as a response from the API, you can then immediately update the single source of truth for that object's data in your store, without having to know its type, or managing data storage where objects have been grouped by type (which is not a requirement in JavaScript arrays/objects, for example).
Similarly, when objects reference each other, a UUID is enough to determine the correct object. When building frontend code, it's really useful to then be able to display and/or fetch data for a UUID referenced elsewhere. One UUID as a primitive object is much easier to deal with than a type-id pair in an object.
Beta Was this translation helpful? Give feedback.
All reactions