Unique component identifier
See original GitHub issueBoth react-async and react-multiplayer need components to have unique identifiers.
In case of react-async — to maintain a mapping from a component to its state and make it serialisable (to send it over the wire, ES6 Map with components as keys can’t be used), in case of react-multiplayer — to have an unique URL per component instance.
Currently both of the libraries use this._rootNodeID + ',' + this._mountDepth
. Should this be added to a public API — getComponentID()
or something?
Issue Analytics
- State:
- Created 10 years ago
- Comments:51 (19 by maintainers)
Top Results From Across the Web
Unique IDs and where to find them | by Anton Korzunov
Unique unique ID. Or uuid. Or just “always new”, never repeatable ID. Useful for generation session keys, transactions, IDs in database, etc. Due...
Read more >Vue.js: How to set a unique ID for each component instance?
Each component has a unique id which can be accessed as this._uid . <template> <div> <label :for="id">Label text for {{id}}</label> <input ...
Read more >AEM - Generate Unique ID for a Component - Suren's Site
For example, if we need to add unique id's for each element in a single component (like multi field component where we can...
Read more >Universally unique identifier - Wikipedia
A universally unique identifier (UUID) is a 128-bit label used for information in computer systems. The term globally unique identifier (GUID) is also...
Read more >AEM Development Quick Tip: Component Unique ID
Often times, you need a unique ID for the AEM component. You either need to trigger custom action with JS or make a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@syranide @spicyj - For those of us who weren’t on IRC - what was the resolution?
2 years after the issue were closed there obviously still demand for a solution and discussion about it. I do not see any reason why the issue should not be reopened.