-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Role and cell clone naming not documented or very clear #222
Comments
related to closed issue: #161 |
Yeah, it's not well documented. As a developer you don't create clone ids. And using them only makes sense for local calls, because you cannot know the clone id of a specific clone cell in other conductors. The only reliable way of making remote calls is using the cell id. The clone index is given by the conductor. It cannot be set by the developer. You could have a rolename as the clone id as you suggest, but it wouldn't be different from |
I'm working with clone cells after a long hiatus. With fresh eyes, I'm remembering how painful I found the ergonomics:
This should probably be changed in the holochain repo rather than the client lib. |
indexing of clones. (rolename:integer) to make a "clone_id" is undocumented and a bit unclear
I think it would be useful to have a common unique field which abstracts above all cell types (stem, clone, provisioned)
to reflect a role instance (useful for DX in the UI eg dynamic store creation) . It could be just rolename.
the exisiting "name" field in all cells could continue to be used for user defined (optional) application logic
for example:
The text was updated successfully, but these errors were encountered: