You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
synapseformation currently only creates or retrieves entities. What should we do about "updating" entities. Lets say we specify FolderA for project, but then decide you want to rename it to FolderB. Would the client:
rename the old folder instead of creating a new one
delete the old folder and create a new one?
The text was updated successfully, but these errors were encountered:
If the entities are identified by name alone (e.g.FolderA) in the input schema, it might be impossible to update entities. I think supporting updates would require a more stable identifier with a separate name attribute that can be updated. Perhaps the stable identifier is stored as an annotation.
That said, how likely will users want to update existing entities? If the project hasn't started yet, it might be easier to manually nuke everything and re-create from scratch. And if the project has started, I would be reluctant to do anything other than carefully move/rename entities by hand.
@thomasyu888: Do you have use cases in mind for updating entities? If not, we can keep this issue around, but wait until use cases come up.
I don't currently have a usecase for updating entities. Although the way that the code is written currently makes its pretty difficult if generation of the template fails midway through.
synapseformation
currently only creates or retrieves entities. What should we do about "updating" entities. Lets say we specify FolderA for project, but then decide you want to rename it to FolderB. Would the client:The text was updated successfully, but these errors were encountered: