Make sure file_history.diff is not null only when change is update_diff#281
Merged
Make sure file_history.diff is not null only when change is update_diff#281
Conversation
Collaborator
varmar05
commented
Sep 9, 2024
varmar05
commented
- Make sure to pass correct diff to File history based on change type
- Introduce DB constraint
MarcelGeo
approved these changes
Sep 9, 2024
MarcelGeo
requested changes
Sep 11, 2024
server/migrations/community/1c23e3be03a3_add_file_history_diff_constraint.py
Show resolved
Hide resolved
MarcelGeo
approved these changes
Sep 16, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.