Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[BACK-815] Implement datum update with historical tracking #579
base: master
Are you sure you want to change the base?
[BACK-815] Implement datum update with historical tracking #579
Changes from all commits
b206d51
6316816
c0a26f6
1415b86
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We ought to ensure datums of a given type can only be replaced by datums of the same type. For example, the code here allows to have a datum with type
food
with one or many history values of typebasal
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you should add an implementation similar to the other methods here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you should add an implementation similar to the other methods here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you should add an implementation similar to the other methods here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you should add an implementation similar to the other methods here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes absolutely all data types are revisionable - this is a big change to the data model and we probably need to confirm this change is ok with Gerrit (who works on Uploader) and Darin (who works on Loop).
Another option might be to restrict this only to certain data types or even to certain fields (e.g. to the fields of the structs that embed
Base
). I'm pretty sure we want to disallow changing the id of a datum.On a different note, I don't think the type here should be a pointer to a slice, because the empty value of a slice is
nil
. By using an interface we lose type safety. I believe the type here ought to be[]data.Datum
.There ought to be validation logic that ensures the type of each entry in the history is valid and of the same type as the base type.