Would it be possible to add a public interface to the Ember GUID process.
no input required just returns an guid that persists for the lifespan of the ember application
You provide the object and it would return a guid that persists so long as that object exists.
These could alias or piggy back off of the private method
Use case: There are occasionally specific cases where it would be useful to have a built in function that can just return a guid. Especially in creating complex D3 charts where you want to easily reference objects and create arbitrary (but unique) ids.
I realize I can just use Ember.guidFor() but because it is a private method, feels a bit wrong.
Welcome hearing any pros and cons. I think I have a general idea of how guidFor works but there may be other framework implications to consider.
Note: moving discussion from Github to Discourse.