Skip to content
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

Handling updates to different assets #33

Open
dbirman opened this issue Dec 13, 2024 · 0 comments
Open

Handling updates to different assets #33

dbirman opened this issue Dec 13, 2024 · 0 comments

Comments

@dbirman
Copy link
Member

dbirman commented Dec 13, 2024

User story

As a user I might modify the state of a QCMetric in a different asset than the one that I loaded in the portal. Should the portal push that update back to the original asset?

I think we do have to sync at upload time, otherwise if we rely on the indexer to sync assets we run the risk of having someone update two different assets and then we need to do merges (in practice the merge is trivial since everything is timestamped, but form a user's perspective it might not be obvious what happened).

[tbd]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant