javascript - Is it a good practice to use ES6 Symbol as unique ids? - Stack Overflow

admin管理员组

文章数量:1341417

Since Symbol is a unique and immutable data type, a mon use case for Symbol is object properties. However, is it a good practice to use it as a unique id? For example:

        const list = [
            {id: Symbol()},
            {id: Symbol()}
        ]

Since Symbol is a unique and immutable data type, a mon use case for Symbol is object properties. However, is it a good practice to use it as a unique id? For example:

        const list = [
            {id: Symbol()},
            {id: Symbol()}
        ]

• javascript
• ecmascript-6

Share Improve this question Follow asked Sep 3, 2015 at 6:15 wuctwuct 10.5k22 gold badges2121 silver badges2222 bronze badges 3

• 2 It's not really what they're made for, and you could use any object. {} != {} – lyschoening Commented Sep 3, 2015 at 7:40
• @lyschoening {} !== {} would not work if we want to maintain an immutable object. – wuct Commented Sep 3, 2015 at 14:38
• @ChingTingWu: Object identity is immutable. If you want the objects themselves to be immutable, you could still freeze them. – Bergi Commented Sep 3, 2015 at 16:47

Add a ment  | 

1 Answer 1

Sorted by: Reset to default 15

This depends entirely on your needs. If you only need them as an identifier in your own codebase, they're fine, certainly better than generating a random ID.

A major downside to using Symbol() though is that they aren't serializable. There isn't a way to share the value of Symbol() across networks/processes or save them to disk/databases.

For most cases it's probably better to use auto-incrementing IDs.

本文标签： javascriptIs it a good practice to use ES6 Symbol as unique idsStack Overflow